lpapez
lpapez on Hacker News
This. The discussions on this site are typically oblivious to this fact. I am desperately trying to persuade a corporate client to adopt version control and here people are talking about Rust. It's like we are living on different planets.
Surely you realize that the codebase behind the language powering 60% of the web is a bit more complicated than an experimental JS runtime?
Talked to my clients this morning and persuaded most of them to shut down the services and wait for the patch. For most of them it's cheaper to lose a day of work than to pay for recovery. Scary to be in a situation where you have no fix/workaround in sight.
Exactly, and you need to start turning a profit before the end of that runway. Even if that means running code that is suboptimal.
This is the right way to deliver software.
Produce working product first, validate the idea, stabilize the business, start generating profit, and then you can start optimizing your costs.
In fact optimization is by far the easiest part of the process because there are many system programming experts on this HN thread who consider these optimizations to be trivial.
Who are you and why should we listen to you banging on the drum?
Memento mori.
You are absolutely right! It was an honest mistake on my part. The absence of colour is the smoking gun.
We are reaching levels of pettiness never considered possible previously.
There is a very good open source conversion tool called "Calibre". I use it all the time to convert my, erm, security backups of books I own.
What is "good code"?
If you ask your boss, it will most likely be whatever spaghetti code which ensures the contract gets signed on time.
The boss doesn't care if the developer needs 10000 libraries for the submit button.
Butcher worker protections and quality of life across all industries to (hypothethically) benefit a single one?
No thanks.
Why do you feel grinding insane hours would be beneficial to AI progress?
It is a comment on the absurdity of orbital data centers. Mountaintop data centers sound absurd, but are more feasible and efficient than orbital ones in nearly every aspect.
Except that is not what the article says and you clearly missed the sarcasm.
If the user puts glue on their pizza because a computer said so, that's a human problem.
The computer generated recipes can be useful as inspiration, but of course common sense is required.
Until Omega Star gets their act together, we have to live with this nonsense...
Can't you simply fill that gap on your resume with something made up? "Self employed", "freelancer", "stealth startup", "confidential employer" etc.
How would the companies ever know?
Very cool research and wonderfully written.
I was expecting an ad for their product somewhere towards the end, but it wasn't there!
I do wonder though: why would this company report this vulnerability to Mozilla if their product is fingeprinting?
Isn't it better for the business (albeit unethical) to keep the vulnerability private, to differentiate from the competitors? For example, I don't see many threat actors burning their zero days through responsible disclosure!
Recommendations from past workplaces and networking. Honestly never heard of anyone else being hired as a solo contributor outside those channels.
> so why use PHP at all instead of JS like all the other vibe coders?
Because there is nothing remotely close to Laravel for JS. I don't want to think about auth, job queues, mailing, cache layers, auditing etc. I want an opinionated default from my framework that is thoroughly documented and part of the AI training corpus. Laravel gives that to me.
>hype-driven commercial product
>single-handedly keeping PHP relevant
While architecture astronauts are clutching pearls, I've built multiple profitable products with Laravel without caring the slighest about the internals, both before and after AI.
PHP was always all about just building stuff while ignoring code quality. Laravel is a natural extension of that approach. Let us live.
> Agile just finally embraced that specs are incomplete and can even be wrong because the writer of the spec does not yet really know or understand what they want. So they need working software to show the spec in action and then we can iterate on the results.
I agree, but what you describe is agile, not Agile (capital A).
Agile (capital A) is Scrum (capital S) where you have Backlog Grooming (patent pending) where the team clears any ambiguity to define a spec (ticket).
Deviating from said spec is seen as Scope Creep (gasp) and might lead to complaints during Sprint Review (trademark).
So yes, agile prefers working software over detailed spec. But typical manifestations of Agile (capital A) are exactly the opposite.
The US public discourse is so dehumanized today that anyone who is not "with them" is literally not a human anymore. Even within the country itself "the leftards" are considered an obstacle which can be removed if only enough force is applied.
Sending armed agents at protesters is seen as being the same thing as sending pest control to clear out beaver dams on the creek. Nobody cares what the beavers think, they are not human, they do not have feelings. They are simply a menace to be dealth with.
You can simply add a shell alias with whatever name you like and move on.
Aged like already spoiled milk.
All of those matter, making this whole situation even more unjustified.
If you only realized how ridiculous your statement is, you never would have stated it.
Amazing idea and execution, the sort of stuff I wish there was more of on HN.
Sure it could have been, if you knew about SSH packet inspectors in Wireshark...
The author didn't, and used a general tool to their aid - why is that unfortunate?