31–40 of 321 posts
Mind blown, if you need to handle "big" data on the move - the macbook neo is not the right choice. - Who would have guessed that outcome?
It occurs to me that there is near zero overlap between people who use a Macbook Neo and people who run DuckDB locally. It would be a surprise if more than 0.1% of Macbook Neo users have even heard of DuckDB. Which means that this article is probably just riding the hype.
That's not tldr, that's just subheader.
This is as much an indictment of AWS compute as it is anything else.
It’s staggering. Jaw dropping. Bandwidth is even worse, like 10000X markup.
Yet cloud is how we do things. There’s a generation or maybe two now of developers who know nothing but cloud SaaS.
I watched everyone fall for it in real time.
This is as much an indictment of AWS compute as it is anything else.
Or am I missing something?
I built multiple iOS apps and went through two start up acquisitions with my M1 MBA as my primary computer, as a developer. And the neo is better than the M1 MBA. I edited my 30-45 min long 4k race videos in FCP on that air just fine.
That's an awesome idea to get a bricked MacBook Neo really fast because those idiots soldered the SSD inside
This is as much an indictment of AWS compute as it is anything else.
> Here's the thing: if you are running Big Data workloads on your laptop every day, you probably shouldn't get the MacBook Neo.
> All that said, if you run DuckDB in the cloud and primarily use your laptop as a client, this is a great device