Live data from Hacker News

Big data on the cheapest MacBook

duckdb.org

171–180 of 321 posts

Re: Big data on the cheapest MacBook

#171

Funny just yesterday I almost bought one but got cold feet and opted for a low range MacBook with M5 chip. The Apple sales rep was not convinced it would be enough when i described using it for vibecoding and deploying so kind of talked me out of getting the Neo. I normally use a mix of LLMs, then connect to Github and do a one-click deploy on CreateOS. Do you think I over-reacted? The price of the Neo is SO attracti…

If you have doubts and you have the money, why worry about it?

Re: Big data on the cheapest MacBook

#172
post #25

Earlier quoted context omitted.

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.

[flagged]

Can’t give up and admit that 8GB of RAM is enough, can you?

Re: Big data on the cheapest MacBook

#173
post #41

Seems completely unnecessary, there is probably 0 overlap between people who buy a cheap MacBook and people running DuckDB locally

It’s necessary because the ignorant keep saying 8GB of RAM is a deal breaking limitation on the cheapest MacBook available.

Re: Big data on the cheapest MacBook

#175
post #136

Earlier quoted context omitted.

> No, you can't do real work on a $350 windows machine. Sigh. I mean, even absent the obvious answers[1], that's just wrong anyway. You're being a snob. Want to run WSL? Run WSL. Want to run vscode natively? Ditto. Put it on a cheap TV and run your graphical layout and 3D modelling work. I mean, obviously it does all that stuff. OBVIOUSLY , because that stuff is all cheap and easy. All the complaining you're doing is…

You mean that machine from 30 years ago that was running 30 year old software that has nothing in common with today’s development? And how well does Linux run on 4GB?

So weird to see this kind of flaming more than a decade after it got stale and silly. I mean, yeah, kinda: a 64MB K6-300 was pretty great!

But as to the 4G quip, that's showing some ignorance of where the market is. The value segment is filled with devices like this: https://www.amazon.com/HP-Stream-BrightView-N4120-Graphics/d...

That's a 16G windows box which will happily run multiple VMs for whatever your deployment environment is, something the Neo is actually going to struggle with. The Jasper Lake CPU is indeed awfully slow, but again for routine "dev" tasks that's just not a limit.

You would obviously refuse out of taste, but if you were actually forced to use this machine to do your job... you absolutely could.

Re: Big data on the cheapest MacBook

#176
post #86

as a broke ecologist, this little computer can do everything I need in R and word and is a phenomenal build for the price. I'm really enjoying it thus far.

How did you get one already? I thought they were just up for pre-order

Mine started shipping on 8 March to arrive on the 11 March release date.

Re: Big data on the cheapest MacBook

#177

I’ve been tempted to buy one and do “real dev work” on it just to show people it’s not this handicapped little machine. 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.

I'm glad enough people got M1 MacBook Airs now that the broader sentiment within the commentariat is changing and people are pushing back on the dismissals.

8gb has ALWAYS been fine in Apple Silicon Mac OS. RAM usage on a fresh boot is a meaningless statistic (unused RAM is wasted RAM). And they're just plain capable!

Re: Big data on the cheapest MacBook

#178

I’ve been tempted to buy one and do “real dev work” on it just to show people it’s not this handicapped little machine. 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.

I was doing Android development and Verilog synthesis on a mobile Nehalem i5 in 2020. That machine is still totally adequate for anything a "normal person" does with their computer, provided they have good tab hygeine. The reality is that (unless you play video games and/or you want local LLM inference) the demands people place on their computers haven't changed significantly in at least 10 years.

Re: Big data on the cheapest MacBook

#180
post #91

When I teach, I use "big data" for data that won't fit in a single machine. "Small data" fits on a single machine in memory and medium data on disk. Having said that duckDB is awesome. I recently ported a 20 year old Python app to modern Python. I made the backend swappable, polars or duckdb. Got a 40-80x speed improvement. Took 2 days.

I'm curious - what were you doing that polars was leaving a 40-80x speedup on the table? I've been happy with it's speed when held correctly, but it's certainly easy to hold it incorrectly and kill your perf if you're not careful

Might be tangential but in my recent experience polars kept crashing the python server with OOM errors whenever I tried to stream data from and into large parquet files with some basic grouping and aggregation.

Claude suggested to just use DuckDB instead and indeed, it made short work of it.

Post reply on HN