verandaguy

    > Improving on Apple Intelligence is something of value

Not if you didn't use apple intelligence in the first place (and/or aren't interested in using it going forward).

    > as is consumerizing local-first AI

If and only if there is actual demand for it. If most users do not want this, it's a bad feature.

Funny enough I went into this site wondering if inland lighthouses were a thing; there are a few obvious cases, like the Netherlands using them to demarcate shoals and for navigation of inland waterways, but then there's whatever Germany's doing...

Just because it's not considered a problem by people without a technical or security background doesn't mean it isn't one.

We make many UX compromises in the name of security, and this is a place where that is most visible.

The solution here is a "keep me logged in for 30 days" or "remember me for 7 days" label on the checkbox, not a forever cookie.

Because in most security models, access is often time-limited.

30 days, for example, is quite long, though NIST does identify 30 days as being the maximum recommended auth token lifetime for low-risk environments.

Higher-risk environments come with 24-hour and 15-minute lifetimes, for context.

Why do they make sense as logon cookies?

    > Every country believes its laws apply universally

This is simply untrue and absurd at face value.

Canada has the Canada Health Act, which describes the specifics of what provinces and territories must provide in terms of public health services, and how, and how those health services are funded, how the money gets disbursed, and how the money gets reimbursed by various parties within the system. It would be absurd to think that the expectation of anyone in the Canadian government is that this should apply worldwide.

The UK has the Highway Code, which describes a number of driving laws, restrictions, conventions, and requirements of drivers, among them, their (at this point rare) left-hand drive rule. Do they expect that to be enforced universally? Do they have some kind of plan to power-project onto the rest of the world with that by having agents of their government travel abroad to, say, France, Mexico, or South Korea, and ticket people for driving on the right?

    > The second is that it violates the first amendment of the US's own constitution, which uses universal language, not discriminating between citizens and non-citizens, nor between inside and outside US territories, nor between nationals and foreigners.

I'll push back against this interpretation since no matter what any country's constitution says, no national constitution can ever really apply to foreign nationals on foreign soil doing their own thing (diplomatic missions being a notable, narrow carve-out for that).

If you take this universalist interpretation, that would mean it's fine for US citizens to truck guns into Canada (which they can't, but they still occasionally do, largely for much more boring reasons than believing there's a constitutional justification) with no restrictions because the implication is that the US constitution supersedes other laws in other countries.

It is, however, against the spirit of the document, and it's arguably an abuse of the existing framework of sanctioning organizations which take part in terrorist efforts. It's another case of the US legal system falling short because of an assumption of good faith by those in power.

At this point...

- I don't think that private-default is a universally (or more importantly, widely) reasonable default

- It adds another case where Rust is unopinionated and gives the user another way to do a basic function.

I like Rust for its unopionation, generally, but I think that the returns for this kind of thing diminish as you get to really boilerplate stuff.

Having worked with rust for nearly two years now (granted, on one team with agreed-upon standards):

- glob imports are rare in my experience, less for the LSP’s sake and more for code self-documentation

- the `mod foo` line exists because omitting it cannot fall back to a reasonable default visibility level (`pub`/`pub(crate)`/<none> (private))

If someone were to list out all the things this admin's fucked up during this term alone we'd be here all day. Seriously; on his watch, there's been food poisoning and child imprisonment; transparent market manipulation; rolling back of various laws and policies which represented protections for workers, marginalized groups, endangered species and national parks; direct participation in the corruption of dozens if not hundreds of US federal agencies; extortion of both US states and foreign nations; threats of violence against strategic allies; waging actual wars of aggression; striking civilian infrastructure and populations during those wars of aggression; engaging in undeclared/irregular warfare; performing strikes against targets which were not clearly combatants; kidnapping a head of state; engaging in warfare and policy shakeups which are timed too perfectly to market close/market open for it to be anything other than market manipulation; engaging in IP infringement against the Nintendo corporation; pushing the morale of the crew of an aircraft carrier strike group so low that sailors were reportedly jumping overboard; engaging in chronic suppression of the press despite the first amendment right to press freedom; reducing or withdrawing the US presence from the ROC and ROK, threatening regional and arguably global stability in doing so; undermining the financial prospects of US beef farmers by federally subsidizing Argentine beef, blaming US citizens for accidents or crimes which in some cases Trump himself may have had a hand in, lying to constituents on a variety of topics (knowingly), deepening the political divides of a country that's already deeply divided, undermining the fairness of both the presidential election as well as threatening to do so to the midterms, supporting the increasing consolidation of US private media largely on the basis of friendliness to the current admin (often as expressed through donations)...

Half of these (or at least, instances of these) happened in the past week or two; most of the rest have happened in the past 2-3 months. I'm not even being exhaustive. You could

"Everything" is an understandable shorthand in this case and while technically hyperbolic it's really understood that it really means "most things that matter on a domestic and foreign policy stage."

... Right.

Did you just create a new account so you could keep arguing with people?

You made yourself an expert in Rust and have never heard of an LSP?

This seems surprising to me given that Rust was one of the first languages to broadly advertise a toolchain and editor integrations which rely on the technology.

I don't know how this relates to my comment, but sure, I guess?

Not GP, but personally I don’t trust claude. Work does for some reason, and work strongly encourages using it, but i stay far away outside of that.

I think every product in this space should have to clear a very high bar for trust rather than making it a race to the bottom with whataboutisms.

It's basically the Torment Nexus meme: https://en.wikipedia.org/wiki/Torment_Nexus

... but I guess some people took this as positive reinforcement.

He has apparently been involved in web technologies since… after i got involved with web technologies. I made my first website in 2003.

Which naturally makes me an authority on the matter. I may have been in middle school but i guess sheer years of involvement are all that counts, right?

EDIT: more to the point, briefly.

Whatever his past successes (or failures), this is decidedly a website which tries to pass itself off as something it is not. If you want to collate information to have a centralized guide, you can do that, just don't name it deceptively.

A specification is a very concrete thing, including in the world of web standards, and someone who's been involved with Wordpress of all things for over two decades should know better than to try and launder the term.

His contributions to Wordpress do not inspire confidence. While WP SEO was no doubt popular (the numbers seem to back it up), SEO had always been a very handwavy thing, and the industry was always full of people willing to profit off that.

To be clear, while I am not accusing de Valk of being such a profiteer, I am staunchly of the opinion that success in the SEO space is not a strong predictor of that person's expertise in any other area of web technology.

To wit, on his past: he appears, per Wikipedia, to have been involved with a site at css3.info. A skim of his author page (/author/admin/) shows that this site had a similar goal, if narrower scope, to the site linked in the HN post we're currently discussing. It was a bad idea then, and it was a bad idea now, and I write this with the knowledge that at least one other contributor to css3[dot]info claims to have been a member of the W3C's CSS3 WG.

And finally, on his Wikipedia page: this is an... unusual page.

- While there's strong off-wiki evidence that he has a presence outside of Wordpress (notably, as a VC), his wiki page focuses almost exclusively on his SEO plugin and the company he built around it.

- By biographical article standards, the article is strange. It focuses much more on a single product than the life of the person being documented, and the vast majority of the article is unequivocally positive. Neither of these are outright indicators of any malfeasance, but are both unusual.

- The principal source for information outside of his career is a Business Insider interview with him which is, again, outstandingly flattering (though nominally informative). The article in effect follows his own description of his life without framing it as such. This is, at a minimum, sloppy writing for Wikipedia.

My overall impression of him, having myself hosted and developed a handful of WP sites in the technology's heyday in the late 2000s/early 2010s: this guy is a marketer with an above-average-for-marketers technology background. I maintain that his website (both website[dot]specification and, to a lesser extent, css3[dot]info) are both at a minimum deeply misguided in their naming and description. My personal take is that, in `specification`'s case, this is a marketing attempt (effectively, an SEO hijacking attempt); it looks legitimate and approachable to web developers relying heavily on agents (and so too does it seem legitimate to agents), and frankly organizations like the W3C just don't have the same kind of presence as they did when HTML5 and CSS3 were new and very, very hot, so newer developers may not know to look for the W3C's drafts.

You'll forgive me for harbouring some pessimism about current world leaders' climate strategy.

This website has been trying to gain a veneer of legitimacy for months now. Half of its contents aren't even published by any real standards body, it's just AI-centric "best practices" for the current generation of hyperscaler models.

The environment's already lost. We've passed the 1.5ºC deviation mark from the pre-industrial global average, and we're on track to hit 3ºC in a few more decades.

The excess deaths and human misery (both that which is increasingly clearly ongoing, and we have to look forward to) are going to be tragic.

It probably comes from the recognition that energy access being a common good, a tax-collecting government should work for its constituents in helping provide energy at a reasonable cost, especially if the subsidies support an improvement to the technology behind it.

Subsidies aren't universally a bad thing. This is silly thinking.

Could that possibly be shielding?

I can't say I've seen it on USB-C-esque cables (except maybe a thunderbolt cable a while back?) but I've seen some cables use a type of aluminum or mylar-looking foil between the outer rubber sleeve and the inner sleeves and wires.

Nah. They're all rotten to the core, just in different ways.

The key difference between xAI and Anthropic/OAI/Google is that xAI has the least-likely path to existing as viable business in a decade.

That said, the economics of the entire AI industry are kinda made up at this point, so who really knows; it's quite possible that the players with the best odds of surviving the crash are those that can draw funding from their parent company's other businesses.

Oh, you mean, when are we going to achieve AGI?

Importantly, webrings are not known to allow their users to live unnaturally long lives, and webring-wraiths have never been observed hunting them.

I always felt similarly about webrings as I did about demoscene. It's less about being strictly practical and more about just a fun little thing you made with your friends. I'd argue that in this day and age, building something from the ground up to be suboptimal by design is a little protest against the quantification and hustle-fication of everything all the time.

Having it be a ring has the nice side effect that anyone closing a ring on your site (or adding your site to it) gets an idea of how everyone in the ring met.

It's more of a fuzzy social thing than a "let's represent social relationships in the most semantically accurate way possible" thing, and for people, I think that knowing how everyone met eachother is a nice thing. You can plan gettogethers off of that. It also keeps people socially accountable; if someone in the group turns out to be a dick, they can just be skipped in the webring.

I'm not sure about the other three, but Bun's rewrite from Zig to Rust was a bit of a joke. `unsafe`s in the thousands, a quarter-million lines of diff, and merged inside a week with no significant public discourse (at least, not much that was responded to by the author).

GP may have been commenting that they don't find this development particularly glib.

I will say that a good solution to this starts before a line of code is written, and does require a PM or scrum master with a deft touch (ideally one who's been involved with the engineering side of a project for a while).

Working with them, the scope can be brought down, sometimes, though this obviously depends a lot on externalities like who the customer is and how much flex they're comfortable adding to the timeline, since that often becomes a factor.

Part of becoming a more mature developer involves being able to navigate these situations with PMs better, and dealing with the frustrations that can often bring (in my experience). I'm still working my way up this side of the job. Historically this stuff has been managed up really thoroughly by my immediate manager (a factor of both the manager's working style, the work being done, and the broader company structure), but my current company structure means that I have to get better at this stuff a lot more actively.