Hacker Newsnew | past | comments | ask | show | jobs | submit | more sesm's commentslogin

The narrative about AI replacing humans is just a way to say 'we became 2x more productive' instead of saying 'we cut 50% jobs', which sounds better for investors. The real reason for job cut is COVID overhiring plus interest rate going up. If you remember, Twitter did the job cuts without any AI-related narrative.


> Lists are accessed only via .at()

If clarity is the goal, then data structures that support access by index should be called `arrays` or `vectors`


[author here] What @joshuamorton said + my rationale was - for natural language users too, a "list" should be more intuitive than `array` or `vector`

I'm more than happy to be corrected though.


The idea of being inspired by natural language is completely at odds with also desiring clarity first


This is very language dependent. People coming from python or Java would call them lists.

Vectors are a mathematical concept unless you use c++.


In Java it’s called Vector / list refers to linked list. Python doesn’t have a linked list type so it’s kinda irrelevant. But also not every language has to be Algol centric even though Algol has largely dominated the design space of popular languages due to familiarity.


> In Java it’s called Vector / list refers to linked list

What?!! No! Vector is almost never used in Java code. When you need index-based access, ArrayList is the much more common one, and it does implement List. So I would agree with parent commenter that List is the equivalent in Java.

A List in Java is a container that allows iterating over items efficiently, but does not necessarily provide efficient random access: https://docs.oracle.com/javase/8/docs/api/java/util/List.htm...

If you care about why Vector is nearly never used: it is synchronized by default, making it slower and more complex than ArrayList. Most Java programmers would prefer to implement synchronization themselves in case multi-threading is required since it nearly always involves having to synchronize multiple list operations at the same time, which cannot be done with Vector.

It's the same reason no one uses StringBuffer, but StringBuilder.


I’m aware. The preferred name is clearly Vector and ArrayList is the wordy alternative they had to use to not break back compat. List is the name to the interface which encompasses a lot of different data types. But ask a Java programmer of they prefer to use arrays or lists and I suspect they won’t even think twice about understand that the list you’re referring to is a linked list rather than asking what you mean because arraylist implements list. A fun Java weirdness is that of course arrays themselves do not implement list


You are really out of touch, LinkedList is very widely regarded as bad for performance in nearly every scenario possible and thus hardly ever used. Array VS Arraylist is a valid question because they have very different properties.


Also why num/num32 for Integer types, and no floating point type


[author here] Very good questions; I definitely would like to revisit num32 very shortly. I'd say the initial rational of having num32 is not coherent right now, but I'll have to verify removing the support.

we have floating point type(It was missing from the type list in readme. I have just updated that seeing this comment. thank you!)


Well, clarity would be achieved with a name like u64. Is num signed? What's the range? Is it integers or floating point? All these things are hidden. With u64 there would be no questions open. (Well a few maybe, like overflow behavior, but can't have it all..)


There cannot be any num32. num is a number, which can be fixed size integers, floating point numbers (of fixed size or not) or bigints. Some also add decimals

num32 being i32 or f32 makes no sense


now we have only int64 for integer types and float64 for floating point types. Thanks everyone for your thoughtful feedback!


Neat !


The big advantage of split keyboards is that a notebook fits nicely in-between the halves.


Secretly? Most blog posts praising coding agents put something like 'I use $200 Claude subscription' in bold in 2nd-3rd paragraph.


"Throwaway prototype" - that's the traditional term for this.


2 pieces of UI in different parts of the page that depend on the same data - that's the line (also matches the initial goal of React - sync FB chat widgets).


> on your own basically

The base (Radix UI) was built by a team on WorkOS paycheck.


Not true. Radix was built by a team on a Modulz paycheck, then acquired and (more or less) abandoned by WorkOS.

Your (implicit) point that Shadcn didn't develop the underlying component library still stands.


It's for projects that are design-first, where you'll have to implement your own component library that matches the design.


In general, Tailwind and React don't match well. Why use a soup of CSS classes when React has props? If someone needs an a11y-focused base for their component library, they can start with Radix UI directly, ignoring Tailwind and Shadcn.


The balance between 'find edge cases' and 'hallucinate non-existing cases and waste your time' may be negative. LLMs are also not free, they cost significant money even today, when they are subsidized by marketing budget.


Even an hallucinated non-existing case (which isn't the norm in my experience) is still food for thought.


It was already shown repeatedly in GitHub repositories in the last year that authors are really unhappy with AI generated pull-requests and test cases.


I am not invested in anything, I am merely sharing my personal experience.


A tarot layout is also a food for thought, but it's free ang gives your eyes a break from a computer.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: