Wes Souza

Wes Souza

@wes.dev

Writing <div> since 2006 · wes.dev ♿️✊🏿🏳️‍🌈🏳️‍⚧️ he/him

1.5K followers421 following511 posts

Back in 2015 I had a server, where I also kept some ancient stuff. I made it into a VM and stored it on a backup. I remembered about it these days. Here's a thread of everything I am finding. First up: Windows 2000.

View full thread

Before GitHub and WordPress were popular (or even existed?), I had a project called MZNews, later renamed MZn², where you could manage news on your website using PHP and MySQL, hosted on SourceForge. I made a box for it on Bryce. (it's true: sourceforge.net/projects/mzn2/)

I apparently made YouTube around 2005. Look at this beautiful UX. Sadly I was poor and used cjb.net, which was not archived. (The videos were using Windows Media Player, this is a recreation of the PHP website by Astra)

Back in 2015 I had a server, where I also kept some ancient stuff. I made it into a VM and stored it on a backup. I remembered about it these days. Here's a thread of everything I am finding. First up: Windows 2000.

Back in 2015 I had a server, where I also kept some ancient stuff. I made it into a VM and stored it on a backup. I remembered about it these days. Here's a thread of everything I am finding. First up: Windows 2000.

If you open a menu fast enough after launching YouTube while playing a video on a nearby TV, the “Now playing” sheet opens INSIDE THE MENU. I’m not even mad, I’m impressed.

The new iPhone Duo (at time of filming) doesn't seem to have any support for viewport-fit=cover, preventing anything from appearing below the vertical bar. Please let this be a bug, and not yet another set of APIs we need to adhere. env(), safe-inset, viewport-fit=cover should just work.

BREAKING NEWS: There are two new feature flags that are disabled by default: Device Posture API and Viewport Segments API. Developing...

The new iPhone Duo (at time of filming) doesn't seem to have any support for viewport-fit=cover, preventing anything from appearing below the vertical bar. Please let this be a bug, and not yet another set of APIs we need to adhere. env(), safe-inset, viewport-fit=cover should just work.

Chrome is expediting two APIs, the Prompt API which lets a website run a small local large language model, and WebMCP, which allows a website to offer MCP support. What if we plug one to the other…

I am vibe coding a news aggregator that moved from a local web server that uses local LLMs on my MacBook to a native iOS trying to use Apple Intelligence models that are crazy aggressive on restrictions to now “let’s just use ChatGPT scheduled tasks to constantly update a site”. Help.

Here’s a small example of why Apple took so long to change Siri to a broader “more” intelligent model. Back in “classic Siri”, I would say “hey Siri I don’t like this song”, and it would correctly mark it, and also skip it on Apple Music. Today I said the same to the new Siri.

In choosing the new Siri, they threw away the old Siri that was extremely reliable (to its own detriment and perceived stupidity). Which one is worse? Both? Hard to say.

At this point I would immediately convert to Catholicism and request religious exemption.

Sam Rose@samwho.dev

With Fable being so expensive, and API pricing only, my prediction is that companies will restrict access to only prompts that have been signed off by another engineer/manager. I wonder if PR will come to mean “prompt review” as well as “pull request” 😅

Today we learned: - oo is one letter - there are two Ps in the word Google - there is 1 P in GsooglePlay - there is 1 P in GsooglePay - the word “Google” is actually the word “Play”

Google, in search, will generate webpages. To anyone. It will show console errors. This, um, won't go well.

Wes Souza reposted

If you ignore the health, ethical, social, moral, financial, environmental, creative, cultural, privacy, quality, legal and geopolitical concerns, then this thing really has legs!!

I feel the same. It’s been extremely challenging to be positive and excited about the technology that is permanently changing everything it touches. And not always because of how capable it seems to be, but because of how convincing it is, and the amount of grift around it.

1/ I’m still processing what’s going on in tech at the moment. I used to feel at home in that world. It used to feel incredibly creative and positive. Now it’s increasingly full of bugs, dark addicting patterns and AI slop. 2ality.com

Wes Souza reposted

write a prompt watch a spinner write a prompt watch a spinner write a prompt watch a spinner write a prompt watch a spinner write a prompt watch a spinner write a prompt watch a spinner write a prompt watch a spinner write a prompt watch a spinner write a prompt watch a spinner write a prompt watch…

Amaze.

VoidZero@voidzero.dev

🚀Rolldown 1.0 is here!🚀 Rust-based high-performance JavaScript bundler. 🏎️ Runs at native speed that’s up 30x faster than Rollup 🤝 Compatible with existing Rollup & Vite plugins ⚡The underlying bunder for Vite After 2 years, Rolldown is officially stable and has 20+M weekly downloads.

As a curious person, I started exploring Google Chrome's `LanguageModel` Prompt API that ships with Google Chrome Beta. I built a stupid harness that sends a system prompt and allows it to eval any JS code it wants. It was fun to play around until I asked what is my user agent...

View full thread

And then I asked "what model are you based on?" It said > I am based on the GPT-3.5 architecture. Funny.

It is kinda sad sometimes, I asked it to "add a chat box ui" and it spiralled failing to produce proper JavaScript DOM manipulations and ended up extremely ashamed.

As a curious person, I started exploring Google Chrome's `LanguageModel` Prompt API that ships with Google Chrome Beta. I built a stupid harness that sends a system prompt and allows it to eval any JS code it wants. It was fun to play around until I asked what is my user agent...

I wanted it to query navigator.userAgent and read it back to me. Something VERY ODD happened. It did a broken tool call, sent the navigator.userAgent as a generic code and then...

It's almost like there's an upcoming event for the company, heavily focused on AI, where product pushed it to be released.

Jake Archibald@jakearchibald.com

So, Chrome's "web standard" Prompt API: Mozilla: Opposed WebKit: Opposed Microsoft: Several concerns W3C TAG: Several concerns Developers: Mostly negative Chrome: Ships anyway. A sad time for web standards. But, I guess someone at Google will get promoted, so 'every cloud…'