I was thinking the same but then I looked at what I could get for 70000 INR on Amazon and it would be crazy to buy this over the alternatives. What is the draw for this device given the price?
If you've tried some of those cheap PC laptops the build quality is no where near macbooks (even for laptops twice the price). Macs tend to live a long time and retain their resale value like crazy compared to PCs too.
I bought a macbook pro m1 pro. Its value is 25% in 4/5 years. I bought a second hand dell latitude 7/8 years ago, it was 3/4 years old then. Still running as a server today. A cheap acer bought in 2017 runs almalinux and is surprisingly fast and capable today, I had upgraded ram and put in nvme SSD long back.
Ive owned a lot of macs and PCs over the last 15-20 years (many of them from work so i didnt "own" them but i used them daily), the % of pc laptops that have technical/hardware issues is way higher than macs in my experience. Of course YMMV with either.
If you are satisfied with the build quality and general longevity of an Acer computer then you are wasting your time trying to understand a huge comparative advantage of the Neo. I’d just accept that you aren’t the market and move on.
Yeah, I guess so. I was just wondering when people said it's great value, is it because they believe that the build quality (all metal) is the most important factor here. But then I can get an HP omnibook 5 oled for the same price with "almost" a metal body.
I started thinking, ok I was going to buy an iPad maybe, why not neo? It makes so much sense since my wife could do much more with it. Then I started looking at what the market has to offer for the price and it stopped making sense. The marketing does seem great on this. I am sure it makes a lot of sense to some people who wanted a cheap macOS laptop and got it.
> But then I can get an HP omnibook 5 oled for the same price with "almost" a metal body.
The bargain HP laptops don’t compare at all to MacBook build quality or battery life.
That laptop is also 4lbs and has below average battery life.
We recently got a higher end HP laptop for someone and the build quality on it is marginal at best.
If you’re only looking at spec sheets and trying to treat this like a comparison table of simple points then you’re going to miss the reason why these products appeal to buyers.
> I bought a second hand dell latitude 7/8 years ago, it was 3/4 years old then.
If your needs are satisfied by 4 year old second hand machines and you’re still happy with them when they’re 10-12 years old, that’s great for you.
I think you’re not the target audience. Your decade old Dell Latitude is not even close to the performance or usefulness of a MacBook Neo so the fact that you’re bringing it up is a good indicator that you don’t understand who the MacBook Neo is for.
The MacBook Neo is a great value for anyone who wants a high quality, long battery life, fast laptop for a bargain price.
I would invite you to read my comment again (take a wild guess what my main machine is from the list) and especially the comment I was replying to (like how the build quality is great for other laptops to still be running as a "server" and a capable laptop). My comment might start to make more sense than you think.
We’re in a thread about the MacBook Neo, so that’s what we’re comparing to.
You said you didn’t understand why anyone would buy a MacBook Neo and then went on to talk about old second-hand laptops. You’re not the target audience.
It might be because of me being relatively new to the Apple ecosystem (I got my first developer Mac in 2020), but to this day I have no idea what is it that it's SO bad about Tahoe.
Not much IMO has changed. I set reduced transparency anyway and that removed the main issues. Some of the corners are overly rounded but that seems pretty minor.
On the other hand, I'm glad people are making a lot of noise about it because it would be nice if Apple could spend a couple of OS cycles on the basics of improved UX.
Systemd is just another init system. People said the same thing about how it can exist with other ones in a level playing field.
By the virtue of having some motivated backers, not only they have pushed everyone out from any distro which matters or acts as a root for others, they have formed a neat little company called Amutable which produces tech allowing anyone to lockdown any installation to an immutable, untouchable state.
Yeap, systemd is just another init system existing on a level playing field. They just dare to be successful by tackling problems that people have today over trying to deliver solutions designed in 1989.
> They just dare to be successful by tackling problems that people have today over trying to deliver solutions designed in 1989.
Thanks for your input. Can you please elaborate about these problems a bit more? I'm pretty new on this Linux thing. Using for just 20 years or so, and managing a quite a few hundred servers only. systemd didn't make my life drastically different or smoother.
Oh, I also used to be a tech-lead of a Debian derivative, and also did some country-wide rollouts of the thing we developed, but I'm sure it has no addition to my already extremely limited knowledge of how things work.
Maybe this is because I'm a noob, or not using enough machines, or not have enough downtime, IDK.
Because well funded projects start to hire developers all over the place to add dependencies and it's very difficult to do otherwise when you have an army of salaried people who do that 40h a week.
Try Sublime Text if you want lower RAM usage. My instance is currently sitting at ~120mb with 3 separate projects open (that does not include usage by Rust Analyzer which runs in a separate process (and tends to use GBs of RAM), but I suspect your numbers don't either)
> Last time I used zed for go development it spawned nodejs servers (downloaded without asking for permission!) for god knows what.
LSPs, they are snagging the LSPs made by other developers for languages you are using. if you install any LSP or language support in VSCode its running the same thing. It only installs when you are using a language that has default support such as Rust, Python (which I believe uses a Node.js LSP), Go (same as Python), etc.
Latency, FPS, efficiency. The LSPs while beefy, are not part of the overall efficiency and are used as sub processes, so if they fail or are sluggish, they won't affect how the editor runs, if you don't want to use LSPs, then you can go ahead and disable those.
Zed is one of the few editors, that like Sublime, are really focused on efficiency, using minimal resources (when needed) and the latency and FPS of the editor is bounds better than VS Code. It just works, better.
I don't know what's going on in this thread. Of course PKI needs some root of trust. That root HAS to be predefined. What do people think all the browsers are doing?
Lineage is signed, sure. It needs to be blessed with that root for it to work on that device.
They're assuming PKI is built on a fixed set of root CAs. That's not the case, as others have pointed out - only for major browsers. Subtle nuance, but their shitty, arrogant tone made me not want to elaborate.
"Subtle nuance" he says, after I've spent multiple comments explaining that bootloaders reject unsigned and untrusted-signed code identically, whilst he and others insist there's some meaningful technical distinction (which none of you have articulated).
Then you admit you actually understood this the entire time, but my tone put you off elaborating.
So you watched this thread pile on someone for being technically correct, said nothing of substance, and now reveal you knew they were right all along but simply chose not to contribute because you didn't like how they said it.
That's not you taking the high road, mate. That's you admitting you prioritised posturing over clarity, then got smug about it.
Brilliant contribution. Really moved the discourse forward there.
I am not getting what that linked url is supposed to mean. It is a very decent business page where ubuntu is selling consulting for "your" projects and telling why ubuntu is great for developing AI systems.
That would make sense if protobuf was complex, bloated, slow. But it's not, so the question should be why not use it, unless you are doing browser stuff.
I am curious about what kind of friction you encountered. Were you generating ad-hoc protobuf messages?
Assuming you were using Protobufs as they are usually used, meaning under generated code, I saw no difference between using it in Javascript and any other language in my experience. The wire format is beyond your concern. At least it is no more of your concern than it is in any other environment.
There are a number of different generator implementations for Javascript/Typescript. Some of them have some peculiar design choices. Is that where you found issue? I would certainly agree with that, but others aren't so bad. That doesn't really have anything to do with the browser, though. You'd have the same problem using protobufs under Node.js.