ctvo

I wouldn’t write Zig off yet. The faster compilation time is a giant moat. Depending on how LLM usage evolves it could be what ends up mattering.

I think Sam Altman is an asshole and I prefer to spend my money elsewhere.

Frontier models being commoditize is inevitable. OpenAI thinks they're still competing on technology, and not user experience and market reputation otherwise they'd understand the continuous negative PR generated by Altman's chaos is going to cost them everything.

The subjective joy is a result of the delusion.

Repeat after me:

_Other people can experience things you do not experience and it is still valid, and not a delusion_. They are not sheeple who fell for marketing.

Carrion Comfort is still one of the most creepy horror books I've ever read and is seldom mentioned when we talk about Dan Simmons.

You listed common items you think may be counterfeits, and all your effort in checking, but fail to mention av single time you _actually_ ran into a counterfeit. I'm sure if it occurred you'd happily mention it since it would do wonders in reinforcing the paranoia.

No. Why the hell would I use Angular 1.x style directives in 2026? For the simple contact form and todo apps, why would I even use client side scripting? Go away.

You've been spamming this in a few threads.

A private business can 100% refuse service to you. Examples with regards to "delegation":

- If you come in using a form of non-cash payment that doesn't belong to you.

- If you're purchasing a car, and are filling out paperwork under someone else's name. FYI, you can buy cars on Amazon.com.

- If you attempt to pick-up a pre-order or an item earmarked for someone else.

...

Of course some businesses are more or less restrictive base on fraud chance, yada yada, but you get the idea. You're not being oppressed. Go shop elsewhere.

top of a regular API

What is the regular API? How do you express all the integrations needed in this API? Who provides the integrations? Answering these questions lead you back to something like an MCP, which is an API contract that can be as generic or as specific as needed. Wasting context window to understand and re-implement each integration is why MCPs exist.

All the security issues are orthogonal, and occur regardless if invoking this API occurs via code or natural language.

... maybe you don't get it?

_Telling the browser how you want the DOM manipulated_ isn't the expensive part. You can do this just fine with Javascript. The browser _actually redrawing after applying the DOM changes_ is the expensive part and won't be any cheaper if the signal originated from WASM.

It's winning by default because _there is nothing materially better_. React was _materially_ better than Ember, Angular, plain JQuery, etc. at the time.

Front-end engineers have no issues adopting new frameworks. See the common complaints about the speed front-end stacks change vs. say Spring MVC or Rails.

A more interesting examination is what is the impact of agentic AI tools being able to write better, more idiomatic code in React vs. Svelte because there's more of it. The human side is less of a barrier here.

And this is good or matters to customers because?

I took a workshop class and was told to setup a track saw. The course didn't bother explaining how to utilize it properly or protect yourself. I ended up losing a finger. I truly hate Stanley Tools with a passion and if I ever need to use another track saw, I'll use someone else.

You're getting a billion applicants because people are desperate and there are tons of CS grads, not because you're the greatest company on earth

How does this change the point? They would still like the best candidate out of that pool, not any warm body, since they have limited positions.

What is your approach to hiring and evaluating talent knowing the large number of applicants and how easy it is to _talk about software development_ vs. _actually developing software_, and how expensive and difficult it is to deal with a bad hire, even in America.

The same reason I’d be uninterested in reading that the Daily Mail wants to investigate something but interested if NYT wanted to.

Has Gamer Nexus produced shoddy work in the past? The comparison feels lazy.

I’m more than happy to read a short sellers investigative piece, for example. You don’t need to be journalists to produce good work backed by facts.

The biggest funders of basic research are those with the most resources. This is your insight? I don't think anyone disagrees. Then you conflate correlation with causation and move it to _monopolies_ fund basic research. Bravo.

As a long time Kagi user, the thing I miss the most is Google Maps integration for search results. It's nice to search for a restaurant or an address, see results for it, and with one click open up Google Maps to see how to get there and nearby attractions. Google Maps is such a large moat for Google, especially in locations that Apple Maps (the only real alternative) has poor coverage.

Outside of that use case, I enjoy using Kagi and recommend it to most people.

It's a great marketing strategy. People without broadband access will truly feel it when they visit.

Consider what companies are launching these days and the talent they need to do it. It's AI companies, it's hardware, it's hard science. It's fewer Uber for pet grooming. There's less appetite for investing in the latter companies and _normal_ software developers are less useful for the former. Yes, ZIRP has contributed, but there are wider economic and social issues that are above my pay grade at play.

The safest space continues to be distributed systems and systems programming in general IMO. You'll still find work at hyperscalers. You'll still find work in the new spaces. Until AI can operate these systems, there'll be a spot for us bit janitors for a little while longer.

Seize or terminate their patents and copyrights. Issue arrest warrants for criminal evasion. Compulsory licensing of x86 to a European design firm immunized by EU law.

My eyes rolled so far back I hurt myself.

Please provide some examples of where the EU has been able to do a fraction of what you listed to large, US based firms in the past.

Looking at the future, if you want a trade war and an excuse for the new US administration to completely neglect NATO obligations this is a great start.

Because the harsh truth is that none of those things are actually big issues that would justify learning slightly different syntax.

That's partially the cost, but the other cost is building this into existing tool chains and deployment mechanisms. Getting buyin from teams, ensuring _everyone_ learns the syntax.

And the unstated fear: The code it generates, is it actually good? Am I going to have silly issues down the road that are hard to debug and require diving into generated code to see some concurrency issue?

Your replies here have been less than useless. I clicked on your profile and saw you were "founder and CEO" of some company.

I guarantee you I won't be using your product. Just something to consider.

It’s insane the excuses being made here for Netflix’s apparently unique circumstances.

They failed. Full stop. There is no valid technical reason they couldn’t have had a smooth experience. There are numerous people with experience building these systems they could have hired and listened to. It isn’t a novel problem.

Here are the other companies that are peers that livestream just fine, ignoring traditional broadcasters:

- Google (YouTube live), millions of concurrent viewers

- Amazon (Thursday Night Football, Twitch), millions of concurrent viewers

- Apple (MLS)

NBC live streamed the Olympics in the US for tens of millions.

Or, hear me out here, it's a wild concept, just work.

You know, like every other broadcaster, streaming platform, and company that does live content has been able to do.

Acting like this is a novel, hard problem that needs to be solved and we need to "upsell" it in tiers because Netflix is incompetent and live broadcasting hasn't been around for 80+ years is so fucking stupid.

But it is simple :)

I think you may mean easy. It may be _easy_, but it's not simple. There are so many more moving pieces, failure modes, operational issues now to consider. Websocket connections aren't free.

I've found that using the websockets extension really helps with automatically keeping the frontend in sync.

I choked reading this imagining people thinking they're doing something simple (as in not complex) by introducing websockets so they can keep state in their Go backend and sync it with their front-end, ya know, to keep track of the # of TODOs checked.

Yes, fly.io is associated with Litestream, but... how is that related to the above thread or this tool?

I wouldn't go around bragging about not caring about people I spend 8+ hours a day with for years on end. It's not the good look you think it is, and you haven't reached some modern level of enlightenment here.

The base is: $284.1K. If you can make it 4 years where the average employment length is a year you can make that $420k. But it will require 16 hour days, luck and some high degree political skills.

This is untrue for Amazon, at least in the US. Your total compensation is guaranteed for the first 4 years. If your total compensation in your offer was 500k, you'll get ~500k per year.

The first two years you're paid in cash so it'll match the offer exactly, the final two years you're paid in RSUs (stock based) with the stock price calculated at the time of the offer. Your salary may vary due to stock price. Historically it's gone up, not down, and this is how people have made 600k+, for example, as a senior engineer there.

Starting from year 2-3, you'll receive new stock grants that will vest in the years after 4 if you stay that long.

Source: I've received offer letters.

They'll do what we've been so-well-trained-for at self-checkouts: the passenger might be given control of the vehicle in such situations (e.g. loss of network connection).

Who handles liability if you get into an accident? When does it take control of the vehicle away? The most likely scenario is the car pulls over safely and asks you to get out or wait.

There are _many_ people who cannot or will not driver. They won't just take over control of a vehicle they're unfamiliar with. Teenagers, the elderly, people without a driver's license, people injured, ...

It takes money to make a robust solution, plus healthy profit, but that money is spread across every customer.

The requirements of supporting the more demanding customers typically are amortized across all customers. Requirements re: security, SLA (uptime, data durability, etc.), data governance for example. It is difficult to both implement and market products that break these dimensions into tiers. You can sometimes do it for the very niche, tail of your customers (air gap regions, for example), but in a lot of products, everyone is sharing in these costs even if they only care about a subset of the capabilities.

The cost savings of scale are offset by the costs of say, needing to support Fortune 100s that need 99.99% availability even if Bob's Wordpress Page doesn't care too much about 99% vs 99.99%. You can apply that analogy to every dimension.

A homegrown solution targets specifically what your company actually cares about. It makes sense that it may be cheaper.

But again. YOU are intelligent, you are informed, you can look and see that Datadog provides a bunch of capabilities you don't need and you're paying for things you don't get benefit from and make the trade-off of building your own. Just stop telling me about it.

Making an argument that there's something abnormal about market competition and that's why prices stay high is different -- I'd read that.