tinco

When I was in university the course was called compiler construction. Making a language like G# is very simple and about the level that the final project of the course would be if the team was working together really well and went for maximum bonus points.

We have so many programming languages because it's a fun and relatively easy thing to start, and lots of people have differing opinions of how it should be done. Also making a programming language seems like a difficult thing from the outside so it has a certain allure.

Swift exists because objective c has archaic language design that modern developers reject. Objective C exists because as far as I know at the time smalltalk style object oriented programming was hip and C++ made the wrong decisions in their eyes. It could also be that C++ wasn't popular enough yet at that point for Apple to commit to it. In that period basically all major operating systems went different ways. The Unix derivatives went all in on plain C, Microsoft went C++ and Apple objective c, though I think OSX itself is plain C for the most part.

I don't know how CarPlay is, but Android Auto restricts the apps and app interactions you can do in the Android Auto user interface. On my phone the only apps that show up are google maps, spotify, and my podcast player and my phone interface I think.

They might, but the final outcome of that depends on whether the tokenmaxxing rust-using zero-user startups are using more memory in ci/cd than the users of efficiently written successful apps are using in production.

Seems like not being compatible with Sentry's agent is a missed opportunity for Appsignal, which I think is the premier EU based (Amsterdam) APM suite at the moment. It sounds like Bugsink is rather barebones in comparison and I bet a quick agentic coding session would make short work of a migration to AppSignal.

Ok so how does he know that? This whole podcast is about how we don't even know how tau clumps and amyloid build ups relate to the progression of the disease.

A transistor effectively is an AND gate. If there is a charge on both the source and the gate, then charge can move to drain. So if you charge up the capacitor and you connect it to the source of another transistor then you can check whether it is still charged by putting a charge to the gate and see if there is charge on the drain.

And you are right, that charge on the drain can then be used both to drive some logic and to activate the recharging of the capacitor that was just discharged.

By the way I am being handwavy about "charge" moving about, if you really want to learn the electronics it is more correct to call it a voltage relative to some ground that the charge always moves towards.

It might count, but it is easy with git as well, what is the feature in jj that makes this easier? Switching branches and pushing changes to remotes is the core feature of git and in my opinion really easy so I'm curious how jj improves on it.

I came into Steins;Gate completely cold. I watched it when it came out and I only just realised there's more to the universe. It's a ridiculously good anime, probably a top 10 for me. It's got a really cool storyline with loads of plot twists, interesting characters and deep mystery.

Never worked at a FAANG, but from what I read from their cultures I don't think a letter to the CEO from a senior engineer would go entirely unnoticed there. CEO's might receive crazy letters, but hopefully not regularly from their senior engineering staff..

No we can't. In the early 2000s we desperately tried to get our governments to be less dependent on Microsoft and we completely failed. Europe is not a federation like the US, worse many of the countries in Europe themselves are governed much like federations. We are easy prey for big American corporations. It's easy for Palantir to sell their product and then a thousand little government organizations will claim there simply is no alternative at the same quality level.

I know it can, but it can't download it faster than the network card can write it into its buffers. That's the part I would count as the 50ms that both can't improve upon.

That's not how anything works. Different languages will perform differently on IO work, different runtimes will degrade under IO differently, etc. That's why even basic echo HTTP servers perform radically differently in Python vs Rust.

This isn't how computers work and it's not even how math works.

What are you disagreeing with? There's some baseline amount of I/O that the kernel does for you, that's what I'm assuming is 50ms, and everything else like runtime degrading is overhead due to the language/platform choice. I'm saying Rust is upwards of 100x faster in that regard thanks to its zero cost abstraction philosophy. You can't just include the I/O baseline in a claim about Rust's performance advantage. You'll be really disappointed when Rust doesn't download your files 100x as fast as the Python file downloader.

Anyway, I'm sorry I provoked your antagonism with my terse messages, I wasn't trying to be blase. I believe uv is the sort of tool that wouldn't suffer much from the downsides of Python and that in most situations the reduced runtime overhead of Rust would have a negligible impact on the user experience. I'm not arguing that they shouldn't build uv in Rust. Most situations is not all situations, and when a tool is used so widely you'll hit all edge cases, from the point where the 10s of milliseconds of startup time matters to the point where Pythons I/O overhead matters at scale.

I'm saying that the Rust might execute in 50ms and the Python in 150ms. You are the one not making sense, we are talking about application performance, why are you not measuring that in milliseconds.

That is assuming Rust is 100x faster than Python btw, 49ms of I/O, 1ms of Rust, 100ms of Python.

Sure, within 100ms. Who cares what the performance multiples are?

It would come pretty close, probably close enough that you wouldn't be able to tell the difference on 90% of projects.

What is more expensive, copying the message, or memory fencing it, or do you always need both in concurrent actors? Are you saying the message passing overhead is less than the cost of fragmented memory? I wouldn't have expected that.

Why couldn't a machine that identifies relations between tokens be AGI? You're imposing an arbitrary constraint. It is either generally intelligent or its not, whether it uses tokens or whatever else is irrelevant.

Also, languages made up of tokens are still languages, in fact most academics would argue all languages are made up of tokens.

Anyway, it's not LLM's that achieve AGI, it's systems built around LLM's that achieved AGI quite some time ago.

Less than 5% of the population knew what it meant to install an app when the iPhone launched. I believe Steve Ballmer ridiculed the idea when asked about it.

A great many amount of people use Android to this day because of its more open nature, and that's despite Google's involvement. If Motorola could go back to its native roots, shake the idea of Chinese influence, and do open source proper, I bet there's a lot more than 5% of the market ready for it.

My company helps companies do migrations using LLM agents and rigid validations, and it is not a surprising goal. Of course most projects are not as clean as a compiler is in terms of their inputs and outputs, but our pitch to customers is that we aim to do bug-for-bug compatible migrations.

Porting a project from PHP7 to PHP8, you'd want the exact same SQL statements to be sent to the server for your test suite, or at least be able to explain the differences. Porting AngularJS to Vue, you'd want the same backend requests, etc..

The Falcon Heavy is $97 million per launch for 64000 kg to LEO, about $1,500 per kg. Starship is gonna be a factor 10 or if you believe Elon a factor 100 cheaper. A single NVidia system is ~140kg. So a single flight can have 350 of them + 14000kg for the system to power it. Right now 97 million to get it into space seems like a weird premium.

Maybe with Starship the premium is less extreme? $10 million per 350 NVidia systems seems already within margins, and $1M would definitely put it in the range of being a rounding error.

But that's only the Elon style "first principles" calculation. When reality hits it's going to be an engineering nightmare on the scale of nuclear power plants. I wouldn't be surprised if they'd spend a billion just figuring out how to get a datacenter operational in space. And you can build a lot of datacenters on earth for a billion.

If you ask me, this is Elon scamming investors for his own personal goals, which is just the principle of having AI be in space. When AI is in space, there's a chance human derived intelligence will survive an extinction event on earth. That's one of the core motivations of Elon.

There was no need for the 15 year old boy who told me this traumatic story of how his sister was killed in his own house to make that story up, because just the fact that they're a liberal family coming from Iran would have been enough information for them to get a visa to stay in The Netherlands based on political persecution.

This happened during Clinton, if you're counting history in US presidencies. And also it doesn't even matter if their sister really was killed. Islamic regimes like the one in Iran are despicable, and would have been even they didn't support goons killing girls for dumb religious regions.

Depends on what you want to hear. The Iranian family in my neighborhood whose father was a doctor fled after Islamist police cut their daughter to pieces in their own home for dressing inappropriately. That's the sort of non headscarf wearing Iranian elite you'll find with an opinion critical of the current regime. I don't know about ostentatious clothing.

To be fair, working on the Rust compiler is also something to do when you're learning Rust. I guess this person is killing two birds with one stone.

If something is literally incredible, then it's prudent to stop and consider whether it should be believed or that you have made an incorrect assumption. In this case, you wrongly assume that Musk is somehow being rewarded for something that happened in the past, or for something that might not even happen. The reality is that the pay package will only have value if Elon manages to dig Tesla out of the hole.

Despite how much conning you believe Musk has done (I won't refute it), Tesla is a company that actually builds cars, and while the Cybertruck flopped and anyone could see that coming from a mile away, that doesn't really affect the Tesla bottom line. That Musk grifted the government into buying them doesn't really do anything besides saving Tesla some money.

I wouldn't buy Tesla shares, I still don't really see their crazy valuation, but I would buy a Tesla car, as they are ostensibly awesome. If you disregard all the lying Musk has done it's still an epic car with unrivaled self driving capabilities.

That he starts talking about something historically has been a sign that some part of it is going to be a reality. You can stand apart from the crazy people who worship the ground he walks on, and still appreciate that he accomplishes great things. Whether it's through conning and grifting, or hard work and keen insight, there are still an electric car company and a rocket company where there weren't before.

Just stop reacting to people believing or shouting things or grotesque behaviors, and just look at the actual reality. It'll do you a lot better than just believing everything Musk says is BS.

The GP was talking about Unreal Engine 5 as if that engine doesn't optimize for low end. That's a wild take, I've been playing Arc Raiders with a group of friends in the past month, and one of them hadn't upgraded their PC in 10 years, and it still ran fine (20+ fps) on their machine. When we grew up it would be absolutely unbelievable that a game would run on a 10 year old machine, let alone at bearable FPS. And the game is even on an off-the-shelf game engine, they possibly don't even employ game engine experts at Embark Studios.

I wonder what's worse, the SFBA-style software development, but also with SFBA-style 2 hour response window to serious bugs like Discord showed, or the old fashioned enterprise report your bug and within 2 months you'll receive an e-mail confirming your report if you're lucky and a letter from a lawyer if you're not.

Yeah it has on occasion, you're right in that it usually doesn't have much of an effect but every once in a while it does. If there's enough of the self-sacrificing users they'll together save a business or a way of doing things. Like running Linux on consumer hardware, or using cash in retail stores.

They don't necessarily have to coordinate, they can use a thousand different linux distro's and literally never talk to each other, and still cause PC manufacturers to keep to a standardized boot process and largely documented hardware so that Linux remains viable.

The author doesn't mean that the technologies weren't inevitable in the absolute sense. They mean that it was not inevitable that anyone should use those technologies. It's not inevitable that they will use Tiktok, and it is not inevitable for anyone, I've never used Tiktok, so the author is right in that regard.

If you disavow short form video as a medium altogether, something I'm strongly considering, then you can. It does mean you have to make sacrifices, for example Youtube doesn't let you disable their short form video feature so it is inevitable for people who choose they don't want to drop Youtube. That is still a choice though, so it is not truly inevitable.

The larger point is that there are always people pushing some sort of future, sketching it as inevitable. But the reality is that there always remains a choice, even if that choice means you have to make sacrifices.

The author is annoyed at people throwing the towel in the ring and declaring AI is inevitable, when the author apparently still sees a path to not tolerating AI. Unfortunately the author doesn't really constructively show that path, so the whole article is basically a luddite complaint.

The rails bugs weren't about Json parsing, they were deserializing into Ruby objects of classes that had side effects, and those side effects led to RCE possibilities. Since those happened, you'll find any deserialization library, especially in dynamic languages, will have a safe (or conversely unsafe) deserialize function to make it more explicit that there's risks involved.

Unsafe deserialization is a very 2010 Ruby on Rails sort of vulnerability. It is strangely interesting that such a vulnerability was introduced so late in the lifetime of these frameworks. It must be a very sneaky vulnerability given how cautious we have become around deserialization since then.