Earlier quoted context omitted.
I'm a bit confused by the "still". How often would you expect to upgrade hardware? Keeping a computer for three years is completely normal for most people.
True… here I’m going wondering if it’s time to upgrade my 2017 MacBook Pro because a couple of keys started to fail and I’m having a hard time…
Ode to the M1
71–80 of 286 posts
Re: Ode to the M1
#72Still running a M1 Air 13“, now into my third job since, and refusing to bother with company provided computers. Still feeling as great as 3 years ago… will only upgrade if the next gen is substantially better (read: not just %faster somewhere). Can comfortably develop on my lap for a full day if needed, only MS Teams draws power like crazy, but apart from that 8 hours+. Best computer I ever had I think.
What do you mean still? They’re only a few years old at this point. It shouldn’t be impressive that a basically new computer still does everything that one would want to do.
Re: Ode to the M1
#73Earlier quoted context omitted.
What do you mean still? They’re only a few years old at this point. It shouldn’t be impressive that a basically new computer still does everything that one would want to do.
It’s not a great thing, but most companies supply employees new laptops every 3 years if they want to keep those employees.
Re: Ode to the M1
#74> Software "engineers" > For every extra cycle an hardware engineer can squeeze out of silicon, you will find a programmer adding one hundred cycles to their program[6]. In other terms, I fear that once devs figure out how powerful the M1 is, they will throw more "features" at it. Can we please stop replicating the "growth" fallacy into software ecosystems? Haven't we learnt enough about how unsustainable and damagin…
For that you need a better alternative. I’m not aware of anything.
Targets Windows, UWP, MacOS, Linux, BSD, Android, iOS, and Web: https://docs.godotengine.org/en/stable/about/faq.html
Nothing says you have to use it to make a game. I recall seeing articles here on HN about using it as a cross-platform app development framework. GDScript may be less appealing than JavaScript, however.
Re: Ode to the M1
#75Earlier quoted context omitted.
It’s not a great thing, but most companies supply employees new laptops every 3 years if they want to keep those employees.
is it rare the decommissioned machines are given back to the employee after cleanup?
Re: Ode to the M1
#76> Software "engineers" > For every extra cycle an hardware engineer can squeeze out of silicon, you will find a programmer adding one hundred cycles to their program[6]. In other terms, I fear that once devs figure out how powerful the M1 is, they will throw more "features" at it. Can we please stop replicating the "growth" fallacy into software ecosystems? Haven't we learnt enough about how unsustainable and damagin…
Electron is quite efficient. You get a modern GPU composited UI, and JavaScript is by far the most highly optimized scripting language out there. The problem with Electron is RAM, disk space, and download size, which is because every app needs to ship its own copy of Blink. This is a solvable problem, but nobody is incentivized to solve it.
Re: Ode to the M1
#77Re: Ode to the M1
#78> Software "engineers" > For every extra cycle an hardware engineer can squeeze out of silicon, you will find a programmer adding one hundred cycles to their program[6]. In other terms, I fear that once devs figure out how powerful the M1 is, they will throw more "features" at it. Can we please stop replicating the "growth" fallacy into software ecosystems? Haven't we learnt enough about how unsustainable and damagin…
Electron is quite efficient. You get a modern GPU composited UI, and JavaScript is by far the most highly optimized scripting language out there. The problem with Electron is RAM, disk space, and download size, which is because every app needs to ship its own copy of Blink. This is a solvable problem, but nobody is incentivized to solve it.
(There basically aren't memory metrics that can show the effect of binary sizes on macOS. It'd show up as disk reads/page ins/general slowdowns instead, but SSDs are so fast that it's very hard to see one.)
Re: Ode to the M1
#79Orbstack I thought https://orbstack.dev/ is what people are using these days instead of UTM. Am I mistaken?
I don't know, but I reject the premise of the question (i.e. there is a consensus). But I'm no pollster. Speaking for myself, to virtualize arm64 *nix on an M1/M2 Mac, UTM has worked whereas other alternatives didn't work for me (such as VirtualBox). I haven't put my hands on the glowing orb yet; I'm sure it will be mesmerizing and tell me to do things like watch Inception (inside a VM) ^ 4. And Orbstack has a compar…
The arm release is a "whoops it got out before it's ready" moment, and the current status apart from being buggy and slow, is that it only runs 32bit x86 VMs on arm.
Re: Ode to the M1
#80> Software "engineers" > For every extra cycle an hardware engineer can squeeze out of silicon, you will find a programmer adding one hundred cycles to their program[6]. In other terms, I fear that once devs figure out how powerful the M1 is, they will throw more "features" at it. Can we please stop replicating the "growth" fallacy into software ecosystems? Haven't we learnt enough about how unsustainable and damagin…
Electron is quite efficient. You get a modern GPU composited UI, and JavaScript is by far the most highly optimized scripting language out there. The problem with Electron is RAM, disk space, and download size, which is because every app needs to ship its own copy of Blink. This is a solvable problem, but nobody is incentivized to solve it.
For example all Electron apps I use have their own implementation of a spell checker rather than hooking into the system one. Normally in Mac OS if I add a word to the system dictionary all apps will learn that word, but in each Electron app I will have to do it again, and again, ...
Many also implement their own UI widgets like basic buttons and input fields whose UX is not at all in line with native apps.