Hacker Newsnew | past | comments | ask | show | jobs | submit | nullstyle's commentslogin

That reminds me:

I got cajoled the other day that I need to upload my ID and ask for 5.5-Cyber access by the Codex desktop app while I was having it develop a fuzzing suite for an open source library I'm(we?) are developing. I was able to berate it into getting back to work.

This struck me as a point of emergent enshittification; an anus if you will.


The company doing the actual ID verification (KYC) is probably the last company I'd trust with this kind of data.

To circumvent conversations being flagged as "cybersecurity bad!!!" I often have to use previous models (5.3 for example, and sometimes using them through subagents is enough). And when this method no longer works, local models will be good enough for it to not be a problem (for my use case, at least).


Prusa sat on its haunches for a decade, happy to leave progress on the table as long as their salaries got paid. Bambu actually got non-technical people into the hobby and has always had more bang per buck.

Buy a bambu; use Orcaslicer

Edit: didn't mean to say "held the industry back"; I would categorize my opinion more along the lines of "were happy to get fat on past offerings" or the like.


Prusa is generally like Apple in that regard, in that they wait for the new technology to be tried and true before committing their design(s) to it. CoreXY is the most prominent example.

Prusa was actually the "non-technical" printer company for quite a while though. They would sell to schools and libraries, and still do, and offer(ed) assembled kits.

I don't own a Prusa, I've assembled Vorons and have a highly-modified Ender 3 S1, but if I was in the market to get a user-friendly printer, or recommend one, I'd get a Prusa.


My thing with bambu was always that they polished whatever the industry (and hobbyists) had invented and closed it all off, then also innovating on top of that but never giving back unless they _had_ to. Polish and mechanical design are great but corexy kinematics, input-shaping are imo what made the X1 stand out as the fast+good-qual printer when it launched. A lot of what they added on top was then to build a moat.

This may be a controversial take, but imo it would be Bambu to set the industry back by a decade if they "win" and lock up the market. That's clearly their strategy afaict.

Does anyone remember Bambu patenting existing open inventions as their own? I can't seem to find good links anymore (?!) but there's some details here https://www.mdpi.com/2411-5134/8/6/141


If no one else is willing to give a polished experience, they have no one to blame but themselves. My father doesn't want to be a 3d printer expert or filament researcher; he wants to print things in 3d as a hobby. Looking back at the reprap, ultimaker, and prusa — the big boys of the maker-oriented printers that i remember — none of them made any progress on making the hobby more accessible to someone like my dad. Bambu deserves some recognition for that.

I never had any problem with prusa default filament settings and printing is easy with prusalink or usb stick.

Prusa is also pursuing patents (they say it's because of Bambu but lol), and they are not releasing their firmware sources for recent printers.

Bambu did not close the tech they used to make their printers. Others (including Prusa) are making CoreXY and they 100% also benefit from the RnD that Bambu did (either hardware, or the slicer (without which Orca would not exist in its current form)).

Bambu just made better products for cheaper and Josef got mad. But I'm certain that Prusa could compete had they focused on making price-competitive polished printers, and not focus on $5k monster printers for enterprise.


How did Prusa hold the industry back? Were they suing other printer manufacturers who innovated?

"Not innovating myself" isn't the same as "holding other's innovations back".


I didn’t say Prusa held the industry back; I said they sat on their haunches. Even the basic differences in stepper motors between what bambu chose and what prusa or ultimaker chose demonstrates my point.

Edit: whoops! guess i did say they held the industry back... my bad /facepalm.


I did quick search and bambu p2s seems to be 30% faster than prusa mk4s and few hundred cheaper. Prusa is more accurate, more open and has better spare parts supply. Bambu doesn't have wifi connection unless I use their cloud?

I'm gonna keep using mk4s.


I’ve always got more consistent and accurate prints out of my x1c versus the prusa mk3 i tolerated. Even just the enclosure makes the bambu experience more much more consistent in my experience

The enclosure is the real added value, hardware-wise; and the H2D has even better environmental control (active heating and cooling of chamber).

While the open-source part of me loves the more open nature of Prusa, the commercial-minded part loves the immediate convenience of the Bambu. But the environmental control is something which Prusa doesn't really do well yet. Heated chamber, as well as filament humidity control is something Bambu has done which Prusa has not, and when it comes to printing with "engineering" filaments like PA6CF, PA6GF and other higher-end lubricating plastics for bearings etc, along with support filaments like PVA which are incredibly hygroscopic, the Bambu is the only contender if you want high-quality prints that don't warp.

IMO this is where Prusa gave up the race and need to catch up. Give me equivalent or better environmental control, and I'll be happy to consider it.

The accessibility to non-experts, and the fact that it just works out of the box without fiddling around optimising settings, is why I have a Bambu family at work and zero Prusas.


Worth noting those are essentially different "generations" of printers, as well as different kinematic systems, CoreXY vs Cartesian.

The Bambu Lab P2S is a CoreXY printer, and that's why it's physically faster than the Prusa MK4S which is a bed slinger.

Not back when i was using AWS

Your car had a recall because the wheels might fall off? Which one?


Specifically, this only affected red-edged premium alloy rims that were OEM made but not installed unless you bought them separately. Not an engineering issue with the vehicle so much as those rims may have had a manufacturing defect in certain batches.

The overly cautious recall announcement was promptly clarified to owners by dealerships, and impacted a small subset. (I have a Civic.)


[flagged]


> According to Claude

Please don't do this.

Quote an authoritative source. Not some AI bot known for ~~hallucinating~~ bullshitting.


Posting AI-generated comments is against HN's guidelines.

Most of my vibe coding is in zig, and it has been my experience that Claude and Codex both keep up with zig changes just fine. Every now and then I catch them writing outdated code that they burn some tokens on, but my experience says your local codebases’s idioms will influence what gets generated enough to stop this from being a problem.

I just removed superpowers from my own setup. In my opinion, given the quality of the planning modes in both claude code and codex, superpowers was really just slowing things down and burning more tokens than vanilla.

Thank you for the data point.

To give back as much as I can, I use the two built-in CC review processes when appropriate. But, those only do "is this PR good code?"

Far too late did I finally roll my own custom review skill that tests: "does this PR accomplish what the specs required?"

If I could ask for one more vanilla CC skill, it might be that. However, maybe rolling your own repo-aware skill via prompt is better?


It never worked well for me. The only thing I really needed outside of the harnesses was a better plan review surface. https://github.com/backnotprop/plannotator

anecdata, but I ended up in the same spot.

I used superpowers - but it burns waay more tokens for basically the same outcome as a single line that states

"Please do planning and ask any required questions before implementing.

[my prompt]"

On the latest models and with a decent harness, the planning modes are quite good, and the single sentence telling it to ask you questions lets the model pick the right thing to ask about, instead of wasting a bunch of time/tokens on predefined skills that try to force basically the same result.

It does introduce a second set of required interactions, but you can have another agent be your "questions answerer" if you need it (result quality goes down a bit vs answering myself, but still quite good, especially if you spend a bit of time on the answerer prompt)

Basically - things are moving fast enough I'm not convinced buying into superpowers/agentskills/[daily prompt magic beans]/etc tooling really makes sense.

I'd stick to the defaults in the harness for most cases, and then work on being clear with the ask.


If they thought they would succeed, no doubt oracle would sue. I expect bad behavior from multinationals, especially oracle

They would not even expect it to succeed, just make an example of the company (the lawsuit is the punishment) to discourage others.


You think normal folks should have access to precision guided munitions and chemical weapons?


Look, I don't think people should have access to these at all, but at the same time, I think that the average Joe would be a better custodian of these than Trump and Netanyahu.

My hope is that equal access might make us stop treating these things as if they are ok.


This has clearly worked out well with giving guns to the entire US population…


It definitely hasn't, but my argument would be in favor of making regular police forces be unarmed as well, like in the UK.


we have armed police, just not all police are armed


That's why I said "regular police". My understanding is that generally no one (including the police) is allowed to carry a gun in public unless someone already illegally introduced them into play. That's the world I want to live in.


It fell into place for my dense ass when I heard someone muse that inside SpaceX the joke is "Mars == Wars"

True or not, it rings with reality IMO


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: