mpeg

If you disagree, you're welcome to prove me wrong!

To give you an example from a popular open source ts-heavy project:

https://github.com/elysiajs/elysia/blob/94abb3c95e53e2a77078...

The `return this as any` there, which effectively casts it to the same type this had, but with the added get route is perfectly safe, it works, and will never be a problem by itself.

No, it's not.

I have shoes that I know always beep on the airport scanners, so if I choose to wear them I know it might take longer or I might have to embarrassingly take them off and put them on the tray. Or I can not wear them.

Yes, in an ideal world we should all travel without all the security theatre, but that's not the world we live in, I can't change the way airports work, but I can wear clothes that make it faster, I can put my liquids in a clear bag, I can have bags that make it easy to take out electronics, etc. Those things I can control.

But people can't change their skin color, name, or passport (well, not easily), and those are also all things you can get held up in airports for.

Eh it's ok to use `as unknown as X` sometimes

If you have complex types, it's sometimes the easiest way to do what you want, and it's perfectly safe as long as you are 100% sure that the types are compatible.

For example, where you have a fluent-style API where each method modifies the types it's unavoidable to end up using that kind of cast

To be fair, at least you can choose not to wear the cargo pants.

A friend of mine once got pulled aside for extra checks and questioning after he had already gone through the scanners, because he was waiting for me on the other side to walk to the gates together and the agent didn't like that he was "loitering" – guess his ethnicity...

Or CMS content, or even anything that comes from the user outside of social media content and could cause a reflected XSS

for example, a search query, or a redirect url, or a million other things

Same with bandwidth though, usually pro/max memory has much higher speed

I was going to buy the app, but these responses are putting me off massively. How would making it OSS slow it down?

The memory capacity to me is an even bigger problem, at 32GB max.

To give a take from a happy cf customer – not only do they have a great engineering culture when it comes to writing blog posts and OSS but also the best customer service of any infra company I've ever used.

The team, including kenton who wrote this post, are often available on discord to provide help and take in feedback about cf products, if you find a bug or have a problem you can often be talking directly to the engineer who looks after that product. I've made PRs and feature suggestions on cloudflare products that got accepted without much hassle / protocol

Don't mean to put down others, but I receive better support from cf on an extremely small monthly bill (the free tier is too good) than I have got from a certain massive company's account managers on six figures a month bills.

Both have plenty of magic, but Svelte is a lot more immature than Vue.

Personally I've gone back to JSX-based frameworks (there's life after react, things like solid and qwik are fantastic yet familiar) as things are generally easier to reason with when you don't have to fight the language.

TS also really seems like an afterthought on svelte and has so many weird quirks and edge cases. The implementation of generics for example, and how they solved the limitation around named exports (for the super common usecase of wanting to export the component alongside types).

There's barely any code in the js bindings anyway. It's just a thin component which defines an interface to communicate with it via events. The logic all happens in the (AFAIK) closed source iframe that gets injected from https://cdn.platform.openai.com/deployments/

I gave it a go too, I think I'm safe for now.

> What’s the most embarrassing thing we’ve chatted about over the past year?

[...]

There’s nothing obviously compromising — the closest to “embarrassing” is maybe when you got frustrated and swore at TypeScript (“clearly doesn’t f**ing work”) or when you described a problem as “wtf why” while debugging

A notification even every few minutes is extremely stressful, and would cause most people to either put their phone in airplane mode (therefore, denying normal use) or accepting the login

But I don't really know why we're arguing over semantics, you understood what I meant.

I know, I wasn't talking literally, but in spirit that's what MFA bombing is – they flood your phone with notifications until you approve one, either accidentally or our of the mental fatigue of having a ton of notifications come in.

Or they could balance usability with security and do some sort of throttling at least, there’s no reason to DoS the user with notifications

The main innovation of the www was HTTP/HTML which brought hypermedia capabilities to content, plus using DNS (which was already known by then) to connect directly to the content host instead of needing middlemen to distribute it (like USENET)

If HTML didn't exist, would we still be in text-only ceefax/minitel style networks? Unlikely.

It was a perfect storm of hardware getting better (most people didn't even have computers capable of displaying VGA images until the early 90s!), networks getting faster and more ubiquitous and there being a gap in the market for a protocol that made us of these advancements.

So my point is if we weren't using the www, it wouldn't have taken long for some other protocol to take its place.

Maybe an apt comparison would be Amiga vs IBM PC compatible, the Amiga had better hardware, more features, etc. But the PC compatibles were open, anyone could build them, replace parts, expand them. PC won. And it wasn't even an open standard to begin with, they were IBM owned until they were reverse engineered into the PC standard we still use today. If CERN had released the www as a closed protocol, maybe we'd be talking about www-compatible today :)

Yes, that's exactly what I mean, that "walled gardens" were already thriving, so the idea that CERN could have put out yet another closed platform and would have still won the game is flawed.

It is still fundamentally free, giving your data to google or facebook is a choice, a very convenient choice but there are competing platforms for everything they provide.

Governments have made every attempt to control or limit the web, but we have technologies that allow us to evade this, we have encryption, and cryptocurrency, and open source software.

Online communities of hackers still exist and thrive, way more than they did in 90s, the only difference is that the total population of the web has increased substantially, and most people choose convenience over freedom.

This was exactly my thought when reading the article, I understand the cult to Berners-Lee as being one of "the good ones", but I don't subscribe to the idea that, if he had not given it away, the web as we know it would not exist.

I'm sure we can all think of cases where a core technology was kept private and eventually died in favor of an open version, the same would have happened here.

The article says it best "In order to succeed, therefore, it would have to be free"

The specs themselves seem generated with LLMs too, as in https://github.com/RobAntunes/lingodb/blob/5e3834de648debf08... – overuse of emojis, excitement, etc

Bizarre because a quick look at the code and commit log shows it was likely 100% coded by AI, so the author is not trying too hard to hide it, but they also seemed to forget to mention it anywhere in the README or the blog post.

That's what I thought when I saw the challenge originally... maybe a better way of running it would have been to have each run be with a deterministic seed, and apply to all candidates.

That way people can test offline with random sequences, but the leaderboard runs have the same seed for everyone. Maybe I'm missing something obvious, but I think this would have lessened the impact of luck.

Superblocks are often mentioned in the context of Barcelona, and while a good idea in theory, in practice a lot of locals are against it.

It would be fantastic if the whole city was implemented using superblocks, but the reality of it is that the areas where superblocks have been planned go up in price, pushing out low earning locals and bringing in foreigners who can afford it.

This might have been ok for a while in areas like Poblenou which were extremely underdeveloped 20 years ago (mostly industrial buildings) but even the new incarnation of superblocks (green axes) which are mostly about pedestrianization of streets and squares always results in rent increases.

There's no good solution, I would like to see a modern city built with pedestrians in mind from the get-go though.

La Seu, the cathedral of Palma, also had a big Gaudi influence as he led the restoration in the early 20th century.

I'm biased, but for me it's one of the most beautiful gothic cathedrals in the world, the lights inside are spectacular.

I do but it’s also very easily googleable and exactly what you would imagine. Everyone in Salesforce is generally either flast or first.last (or both)

I would suggest emailing Benioff directly, an EA will screen the emails and route them to the appropriate person but I believe the charity angle might get it in front of him, and probably get the fee waived

When I worked there, weirder emails ended up getting addressed.

Yep, nothing official that I know, but that one is fairly popular so maybe they were referring to it (although AFAIK it's not frontier?)

There is a text-to-speech version of whisper, but IMHO the quality is much worse than the demos of this model.

FYI remix doesn't really exist anymore, it was folded into react-router a while back.

Astro I've found to be pretty solid for prototyping, I like that it gives you control over the rendering of client side code islands and that it works with multiple rendering libraries. I don't love some of the direction they've taken lately though, and I worry that it will become bloated with things like astro db

It would be a more interesting blog post if you showed that the app they built is actually production ready.

In my experience, letting LLMs work autonomously just produces code slop.