HackerThemAll

It's an alpha phase. Why you people consider a project that is being actively developed for only couple of weeks a finished product? It's improving on a daily basis. Adobe and Microsoft had several decades. You're asking for the same in order of weeks? And for free? Is it me who is unreasonable here?

> We see nothing.

Clear your glasses. For example - https://getartcraft.com/apps Thanks to those people we may soon have great alternatives to monopolies.

> there's no way a C web server will be free of RCEs in today's world.

That's a bold claim not supported by facts. The following one had not had any RCE for 27 years, since its inception, and counting. I am certain there are more C web servers written securely.

https://cr.yp.to/publicfile.html

I like everything about it EXCEPT the Apache HTTP Server (if I understood the article correctly). It should be discouraged nowadays. Its lack of progress, lack of features, poor performance and lack of security makes me never consider it again.

To give you more context. I recently closed a security gap in a customer's web server that most likely resulted in a data leak. That web server stored (of course) database backups and other personal data. The directory listing was visible and accessible from the open internet, because - note that - the .htaccess file where the access was disabled had INVALID END OF LINE CHARACTERS according to Apache (and it wasn't me who prepared it in the first place). Therefore - note - the server IGNORED that file and its default setting was OPEN ACCESS and enabled directory index. It's wrong on so many fronts. The Apache's philosophy is not "I cannot parse the config file, therefore I disable access to the directory tree until administrator notices and fixes it". It was not logged in the server logs as "invalid EOL detected". Apache after over 30 years of development cannot parse all 3 end of line sequences - the process which is TRIVIAL to the point of being ridiculous. Deciding not to include CRLF or bare CR is not about performance. It's just the decision of its makers, there's no justification these days. It violates "be liberal in what you accept and conservative in what you send". In 2026, when the cybercriminals are everywhere, just waiting for the data, scraping it all over, the server's default should be "close everything until it's explicitly open" and "if the config is broken, disable access and/or fail".

Yeah, and for the contrary I spotted Claude app being ugly. When I turned off Claude, then put my computer to sleep and later woke it up, it made my fans spin loudly, and after I checked, there were like 2 dozen Claude processes and a lot of Python. What was it doing - I have no idea, but it was crazy. I'm setting up a VM with nothing but Claude and necessary tools. I feel Claude is not honest with everything it is doing.

That's not how it worked in the past. There was no notion of "CI" and usually you installed software by downloading the source .tar.gz to your target server, then doing:

  tar x
  cd <source dir>
  ./configure <options>
  make
  make install
  make clean

Yeah maybe it's less visible nowadays, but in the past the world was not just Linux and FreeBSD. There were many commercial Unixes which differed from each other and from Linux. And to be portable to such systems you needed to check everything. So autoconf was a crucial tool, not just a fancy noop.

I once tried to become a Hetzner customer, but they wanted so much data from me, including photos of my ID, so I said no. No other compute provider requested that much, including all 3 big ones and OVH. Either I was lucky before KYC became a thing, and Google, Microsoft and Amazon inferred my identity from my payment cards, or I don't know, Hetzner is just too paranoid. I lean towards the latter. Yes, recently I created a new account in an another European compute provider, and they didn't want my ID.

So no, thanks Hetzner.

> I would have much preferred SVG diagrams based around static screenshots.

Just take your time to contribute that to the project, it's a win-win.

So on one hand you're lagging 4 years (and 4 versions) behind, but on the other hand it's just 4 years and 4 versions. I like your approach. Without it there'd be no progress. Google has similar policy in many places.

It'll be much harder to replace lost data than destroyed hardware.

Will Trump be able to change the law so that he becomes a lifetime dictator of USA?

DuckDB is the best thing world got since 1990s.

https://duckdb.org/2025/05/19/the-lost-decade-of-small-data....

Hope not.

> It is a direct image link, it wont ask your password.

Have you lived under a stone? No wonder we have so many vulnerabilities if people have no idea about images being malicious, exploiting image decoding libraries.

Choosing a language that forgives bad memory management practices and promotes sloppy programming practices is your decision. Don't be surprised that it has to do its job. You could have chosen modern C++ or Rust and use RAII and proper automatic deallocation.

It was rather towards one-process-per-client such as PostgreSQL server or Apache HTTPd (long obsolete, fortunately). Hopefully PostgreSQL will switch to worker threads soon, and as for Apache HTTPd, I don't care.

> most/every QUIC implementation is poorly implemented for maximizing performance.

bold claim. Go tell that to Cloudflare, for example. And/or show us your implementation.

The reason was the coders' mindset who entered the job market after 2000, maybe up to 2010, that the ability to code (to use a programming language) is the ultimate development of homo sapiens. With that solved by AI, we can safely start going back to simple, sane concepts like low-code and no-code, property sheets and drag & drop user interfaces.

> appearance-wise it looks very noisy/distorted with some crooked elements (especially window buttons) and missing visual parts (mainly bevel edges).

Nitpicking. Let me reflect - runtimeterror.com has no https which is available for free, so I'm not entering it.

> drinking up water for data centers

As long as your law allows it, it's not Google's liability. Just change the law. But you call regulations "communism".

> They have the only vertically integrated AI stack, insane capital

and paying enterprise customers.

> couldn't stand how opaque the process is to see what ports are occupied

Discover shell aliases... You only need to remember "port"...

This is for Linux

  alias port="sudo ss -tulnp"

This is for macOS

  alias port="sudo lsof -nP -i -sTCP:LISTEN"

Yeah I wonder why they aren't used for neural networks. It's been claimed they'd require far less power and they'd offer better accuracy and faster computations, although I am unable to verify that claim.

NASA requires 15 decimals of pi for interplanetary navigation. On the range of 16 bn miles to Voyager 1 it gives them calculations being off by 0.6 inch. For universe-sized circles they need 37 decimals of pi.

Trying to remember 100 digits of pi won't give you any advantage in cognitive functions apart from memorizing 100 digits of pi, for a little while. Better spend your time elsewhere.

https://www.jpl.nasa.gov/edu/news/how-many-decimals-of-pi-do...

the what?

> You buy it because it's what the cool people use.

I apparently define cool people differently :joy:

> Imagine applying for a SF startup job

No, thanks :joy:

I never really understood the craze for the overpriced Apple products. After many years of using PCs with Linux and Windows, I got forced to use a MacBook Pro as the company laptop and I found it hard to use. The OS is so limiting, Finder so crappy, oh my. There are some advantages, like the hardware is good, but on the other hand there are countless tiny issues where "Apple knows better" such as tying mouse scroll direction to the trackpad direction which is awkward for me. And now this what you're describing. So no, thanks, I'll stick to ThinkPad.

Yeah that practice is not unheard of. I can easily imagine having a ready-made device to desolder the original chip out of Raspberry and solder another one, of poor quality and/or counterfeit, and then sell that modded Pi for profit. Heck, remember fake SD cards, USB drives etc.

Therefore I agree with manufacturer's decision.

I'd happily see performance, latency and stability of your allocators in massively multithreaded, long-living programs with workloads where hundreds or thousands of parallel threads continuously create and destroy short-lived small and medium objects.

Writing allocators for domain-specific access patterns is easy. Writing a general-purpose high performing, stable allocator with bounded P99 latency is hard.

Give your friend, Dunning–Kruger, some better pills to keep him from speaking through you.