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

I was rebasing and thought I had committed some kind of git sin that I wasn't aware of.


Point me at a processor as good as the M1 and I'll buy it


Define good? An AMD Ryzen 7 6900HS has similar single-core performance, much better multi-core performance for slightly worse power efficiency, compared to an M2. Add in the added advantage of flexibility (you can buy different hardware and switch it up like add RAM and disk and GPUs to your liking) and the fact you can run more things on it (e.g. game), and it's pretty "good". Is it better than an M2? Depends on what you're looking for.


>> slightly worse power efficiency

I don't believe it. My M2 Max maxes at around 40W. x86 just isn't that power efficient. You can idle with only one/few economy core turned on running at the lowest power state for longer battery life but x86 is simply very hungry when running high loads and it can't be magically improved. The arch is just obsolete and legacy.


slightly worse power efficiency is a slight understatement ;)


I am forced to use it and it is hot garbage. It is a productivity killing anti-app.


It's got the most confusing, designed-to-lose-stuff UI I've ever seen. And that includes major social media sites, Atlassian's whole... pile of stuff, and (its closest competitor I've come across) a very "advanced" set of Asana projects and workflows.


Yes. This is the way.


You are living in an absolute dreamworld. I give manual transmission 15 years tops.


or, better yet, stop using this


types are so synonymous that there is no reason to use interfaces in TypeScript.


There are several reasons to use interfaces in TypeScript:

- they perform better at build-time and in editor

- they have more relaxed rules for recursion

- they can help identify complex types and distinguish them from simpler ones

- they’re guaranteed to be usable to enforce class implementations, whereas only simple types can be used

- they’re much easier to read in type errors


> - they have more relaxed rules for recursion Do you have a source for this? I would like to read more.


I would be impressed to see readable, non-trivial TypeScript code that does not use Interface.

Unless you are referring to interface as a concept, and not the keyword in TS.


Can you use the “class MyClass implements MyType” keyword with types?? That might be the only reason if you can’t


Very alive and well in Canada. Canadian and US culture have many similarities.


How does it become problematic? You just pass in dependencies as arguments to functions or components.


Because classes as a language construct are one big massive footgun on nearly every level.


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

Search: