HN user

noo_u

60 karma
Posts0
Comments24
View on HN
No posts found.

This might be financial prudence of sorts - doesn't something like 80% of their yearly monetary contributions come from Google, particularly for search partnerships? If they are concerned that Google will start paying them less because search has diminishing future returns, diversifying their income sources through investments in AI might be a good idea.

This is a really awesome project! If you have time/interest, you could try to build a simple http server now, that your browser could communicate with. Then you could try to implement a simple version of TCP/IP, and look into how lower level networking works. Great job!

Pandas 3.0 6 months ago

to_pandas has a dependency on pandas - it is not the biggest of deals, but worth keeping in mind.

Pandas 3.0 6 months ago

Polars took a lot of ideas from Pandas and made them better - calling it "inferior in every way" is all sorts of disrespectful :P

Unfortunately, there are a lot of third party libraries that work with Pandas that do not work with Polars, so the switch, even for new projects, should be done with that in mind.

The real question is - did you buy 10s of printers because you needed them for the business, or did you start the business to buy 10s of printers :P

Calling PETG "utterly problem free" is quite a stretch lol. PLA is pretty objectively much easier to print than PETG, and perhaps than all the popular filament types out there, especially if you are trying to print anything where precision/detail matters. .

PETG is just oozier and stickier by default, so stringiness is almost guaranteed to happen, bridging at a greater risk of failure, etc. It is tougher, so unless you have a printer that can use multiple filaments on the same print, removing supports is more difficult.

Can you reduce these factors by tuning your 3D printer - yes, a bit. But that's not "utterly problem free".

PLA is the plug and play of the 3D printing world right now.

I think both of us are ultimately wary of using the wrong tool for the job.

I see your point, even though my experience has been somewhat the opposite. E.g. a pipeline that used to work fast enough/at all up until some point in time because the scale of the data or requirements allowed it. Then some subset of these conditions changes, the pipeline cannot meet them, and one has to reverse engineer obscure SQL views/stored procedures/plugins, and migrate the whole thing to python or some compiled language.

I work with high density signal data now, and my SQL knowledge occupies the "temporary solution" part of my brain for the most part.

I'd say the author's thoughts are valid for basic data processing. Outside of that, most of claims in this article, such as:

"We're moving towards a simpler world where most tabular data can be processed on a single large machine1 and the era of clusters is coming to an end for all but the largest datasets."

become very debatable. Depending on how you want to pivot/ scale/augment your data, even datasets that seemingly "fit" on large boxes will quickly OOM you.

The author also has another article where they claim that:

"SQL should be the first option considered for new data engineering work. It’s robust, fast, future-proof and testable. With a bit of care, it’s clear and readable." (over polars/pandas etc)

This does not map to my experience at all, outside of the realm of nicely parsed datasets that don't require too much complicated analysis or augmentation.

Did I use the word "all" anywhere in my comment? There are good developers in Europe. What I am saying is that there would have been even more of them had the incentives not been so lackluster. More talent seems to generally result in a greater competitive ability.

Fwiw, I have doubts that currently Europe can compete with the US at the startup level, let alone at the bigco one.

I am not trying to drag Europe down - it worries me that sophisticated complacency, overconfidence based on the achievements of previous generations, and addiction to comfort, will start eroding the very aspects that make it a great place to live at.

It is, at this point, an easily verifiable fact that software engineering jobs in Europe are en masse poorly paid relative to the equivalent positions in the US, and the majority of the EU companies that actually pay well are actually US based. This causes a lot of outflow of talent. That VC funding in Europe is atrocious is obvious to anyone who has had to go through it, and have fun letting a poor performer go from your 5 person startup.

Your polite wishful responses are frustrating to read to anyone who's had to go through this hell.

Well both sides could be right, no? I don't think it is necessarily uncharitable to note that lack of experience could cause developers to have strongly held, yet potentially invalid opinions about the practical applications of a technology.

It's definitely anecdotal - and I agree about steering the robot. I find that analysis is harder than creation usually.

Absolutely - one of my favorite uses of Aider is telling it to edit config files/small utility scripts for me. It has prompted me to write more comments and more descriptive variable names to make the process smoother, which is a win by itself. I just wish it could analyze project structure as well as Claude Code... if I end up with less work at work I might try to poke at that part of the code.

I have found that HN is, ironically, a horrible place to post experimental work on, with a few exceptions - e.g. things "written in Rust" etc. I think it's because the majority of the commentators here haven't really made anything from scratch.

"You should remain in charge, and best way to do that is to either not use agentic workflows at all (just talk to Gemini 2.5/3 Pro in AI Studio) or use OpenCode, which is like Claude Code, but it shows you all the code changes in git diff format, and I honestly can't understand how anyone would settle for anything else."

I 100% agree with the author here. Most of the "LLMs are slowing me down/are trash/etc" discussions I've had at work usually come from people who are not great developers to begin with - they end up tangled into a net of barely vetted code that was generated for them.