1,791 karma · joined January 31, 2022
It’s still AI, but it’s not the AI system generating something
Checking against version numbers helps cement existing browser monopolies, makes it difficult for new browsers to view websites (even if the browser correctly implements every feature), and encourages everyone to spoof version numbers / browser names which leads to them becoming a less and less useful signal. See any browser’s User-Agent string for an example of this
Beside this security blunder on Discord’s part, I can see only upsides to using a browser version rather than an Electron desktop app. Especially given how prone Discord are to data mining their users, it seems foolish to let them out of the web sandbox and into your system
GH Desktop's merging, conflict stuff, and (lack of) graph leave much to be desired, but it's already 1000 times better than the git cli. Whenever I have someone who hasn't used git before joining a project, I always get them to use GH Desktop - it's easier for them to understand what's happening, and reduces the messes they cause compared to running random git commands from stack overflow.
1. The one feature I prefer in Marko when compared to Mint is Marko’s nice ID and class syntax, rather than your custom selectors, so you can just use regular CSS (which seems to be advancing faster than the JS & HTML specs combined). You could get the scoping using shadow roots for your components (I’m sure this has flow on consequences, but given you own the language it’s probably better case than many others.)
2. Interpolating values directly in CSS blocks is something that a lot of HTML templating systems sort of give up on (see Astro going out of it’s way to make interpolating variables super verbose [0]), so I’m glad to see you do it. Does the value interpolation compile to CSS variables that are set on the component root (or somewhere else I suppose) as in Astro [0], or is it just simple interpolation? Additionally, I can’t help but notice your hash symbol would conflict with ID selectors, so is CSS nesting available?
Please don’t take this as criticism! I really like what you’ve done here and am very curious.
[0]: https://docs.astro.build/en/guides/styling/#css-variables
As I understand it, Ryan Carniato was a major part of this project, and later went on to lead SolidJS, which goes back to the React style HTML in JS. Has he spoken at all about why he went back to that templating style?
You still need to come up with the circuitry for all the maths and figure out how to represent all the state with red stone, but once you get the little bits done it’s quite a quick process filling in weights and duplicating logic sections
Some of the higher end ones (such as my phone, which is how I know this) have the AM/FM signal processor built into their SoC, but the pins aren't wired to an antena.
They also have a good Google Photos alternative, which is how they make money.
How do they (oklch & oklab) compare for different uses?
If you do want streaming apps, Bluetooth, wireless sharing, etc, you can buy a plugin box/dongle. E.g. a Chromecast, Google TV, or a full-blown AVR.
You can choose which dimensions to show, pick which embeddings to show, and play with vector maths between them in a visual way
It doesn't show the whole set of embeddings, though I am sure someone could fix that, as well as adapting it to use the gpt-oss model instead of the custom (?) mini set it uses.
As I understand it, Mercator mostly preserves relative distances between continents, at the expense of distorting continent shape & size. This is useful for ocean-based trade route calculation, which was a major concern when Mercator was introduced.
Most regions these days have a standard projection they use that best represents their country and modern GIS software can trivially reproject data in whatever format your project is using.
For example, in NZ, New Zealand Transverse Mercator is normally used. We used to use New Zealand Map Grid, which better represents our country, but the govt decided to switch the official one to better integrate with overseas data & software. Modern software allows you to trivially use either though.
Tl;Dr: map projections matter, but different ones are better for different purposes in different places. The African Union can use whatever they want, and everyone else can use what is most useful for their maps. No need for everyone to use the same system when we can use both.
Does anyone have any background information on the authors? Have they published similarly impressive works in the past?