err4nt

The point of Chrome-only CSS (vendor-prefixed features) would be to allow Chrome or any other vendor to expose styling functionality to CSS authors in valid CSS syntax in ways that won't impede future standardization efforts (like writing non-standard CSS would do) or interfere with that same CSS being processed by other vendors.

But this article isn't an example of Chrome-only CSS, this is about a change to the standard select element to make it customizeable in a standard way. It's not fully frozen yet, so they're seeking feedback and still working on it, so if you have input to give about this feature I think they'd welcome it. This blog post was about Chrome introducing experimental support for it, likely so developers can experiment with it and provide more valuable feedback towards its standardization!

Presumably so you can test it on-page

The straw that broke this camel's back was they edited and rewrote an answer I had posted, but left my name/avatar beside what was no longer my words. That was too much for me. I wouldn't mind if they did something like "(MOD EDIT: alternate info)" or removed it if they thought it was incorrect, but I can't be having my face and name next to words I never uttered. I've never experienced that type of mod behaviour anywhere since.

Elections have a deadline after which a new election can be called, but there's no number of terms served that then stops a re-elected leader from taking office if they win another election. It's not the case that people can just stay in office without holding elections forever.

A delightful read, though I disagree. Unless we were going to introduce half-minute units (which decreases the scale of the error, but makes it twice as numerous) then shifting our minute units by a half value doesn't seem to actually solve the problem, doesn't it only shift it to a slightly different location?

Any JSON-compatible data (and even some JavaScript data formats beyond strict JSON types) can be converted to an XML representation, have real XPath queries run on it, and the original matching data returned as the results.

We use this to great effect exploring and sifting through data in web browsers, where many different pieces of software may be storing various things globally, but you don't always know where to look.

(The advantage to this approach is that both XML and XPath are specified standards)

Cool! Hope it works well and convinces more people to try it (if it works out)

There's no way writing illegal HTML is preferable to writing legal HTML.

Here's what the HTML spec[1] says about data-* attributes:

    Custom data attributes are intended to store custom data, state, annotations, and similar, private to the page or application, for which there are no more appropriate attributes or elements.

Doesn't sound like this would be an abuse of even their specified intended purpose, sounds totally within the realm of why the feature exists in the first place: author-defined extensibility within the language.

1: https://html.spec.whatwg.org/multipage/dom.html#embedding-cu...

I wish it didn't require authors to practice doing the wrong thing (writing invalid HTML) for to use the tool.

Authors are free to either create any data-* attributes they wish for any purpose, so long as the custom attributes are prefixed with "data-".

Authors are also free to create any (valid) HTML custom element, and to invent custom attributes for those elements.

But this appears to require authors to write invalid HTML.

Yes, that article was sober and wise. I'm in Canada and I really hope other countries do not follow us down this path. I have fears grounded in facts based on what is continuing to unfold here in a relatively short number of years that very soon the sick, disabled, and elderly will be targeted by MAID, and I fear that after that the marginalized, (temporarily) impoverished, and even non-terminally injured may come into view. Human life is worth more than this!

There's two distinct types of 'AI' fatigue I'm experiencing. The first type is having to see AI buttons showing up in prime places in navigation on every website and app. Even if it's useful, I just want to hide it most of the time.

And the second type of AI fatigue isn't even about the AI technology itself, but it seems like at the same time that people adopt AI in their workflows they often seem to raise their tolerance for made up nonsense. That's not really a problem with AI because we ought to maintain quality standards no matter what tools we use, but so many people were willing to forfeit quality for volume and convenience at the same time as using AI.

Thanks, I think that helps me understand the 'why' a lot more! That's kind of cool, and I do hope they can keep making progress in that effort!

Can anyone explain why they bothered with the fractal at all, instead of using a 3 dimensional grid? Doesn't a grid of the appropriate resolution provide the exact same? Or is it to show that they can do everything within even a subset of a 3D grid limited in this way?

They had literally 1 job: secure authentication. This isn't the first time Okta has had a gaffe on a level that should cause any customer to reconsider. What's that saying, "Fool me once, shame on thee, fool me twice, shame on me". Don't get fooled by Okta a second, third, or fourth time.

see also the section about elective (medically unnecessary) surgeries and procedures too

They won't need to fork WP itself (though they're totally free to do that, WP started as a fork after all), but it sounds like they may need to quickly focus on creating their own plugin and theme marketplaces, and other services that WordPress.org provided to WordPress CMS users but is not denying to WPEngine.

Let this be a lesson to all of us - if you rely on a service provided by another organization external to your organization, get an SLA! Get a contract that guarantees you the provision of services you depend on.

What's the risk? You own the code, and you aren't pre-committed to updating to any new versions in the future. You can just take it and use it on your own forever. Many people do. What's their risk?

The headline is not misleading, though it's not the tree famous for perfume fragrance, they believe it may be close relative used for medicinal purposes!

Some ideas in no particular order:

- Node is still around and still used, so there's less room for Deno unless Node decreases

- Deno fills a slightly different position than Node, in that it's a TypeScript engine and is more aligned with modern JavaScript how it runs in browsers, allowing you to share more code between browsers and Deno than you can between browsers and Node

- Deno users are probably almost all also Node users, while not all Node users may be Deno users

- Some of the people who might be interested in Deno compared to Node may also be interested in other runtimes like Bun and QuickJS

I don't think the size or popularity of Deno are a problem and I think more and more people will enjoy it in the future as time goes on.

If you click the link under his message that says 'parent', you can see the comment he is replying to. I don't think there's a way to see both at once very easily because of the number of replies the parent comment has.

If they were aiming to please web developers, they took a wrong approach. Their syntax highlighter by design is incompatible in its approach to parsing CSS to be able to syntax highlight it correctly, and this was pointed out to them early on and they just hacked something broken together. It didn't appear to be a serious attempt to support web languages.

It's so funny but encouraging to read this. I started drinking coffee in college and could easily finish a whole pot, or have 3 Starbucks venti drip coffees in a day, but I was not sensitive to caffeine at all and could sleep right after. It also didn't seem to have that wake-up alertness effect either

Then something changed, and now I am sensitive to it like a normal person. It does wake me up after a sip or two I can feel it, and I can easily have 'too much' if I have 2-3 cups in too short of a timespan, so I've had to learn to slow down.

Having said all of this, my personal 'last call' is 6pm, with the idea that I will be able to sleep at 12-1am. But if I drink coffee after 6pm I might be delaying that bedtime a little.

It will be interesting to learn more about the effects of how much, and how long. Should I be tapering off hours before 'last call'? What is the best 'last call' time in the day and should it be earlier? I'll have to track some of this and figure this out!

As long as you're consistent enough, if you use this tool for a while could you learn how to tune the value it gives you? E.g. if you know you need extra time, or less time you can take that into account when reading this.

I agree with your perspective, it does come across like someone who has had success learning one stack and that's great, but it's hardly a picture of the varied landscape. There's nothing wrong with PHP and I've seen plenty of businesses do just great with it. I've also seen companies doing equivalent with Ruby, and Go, etc, and even a mix of languages. You can do all this without falling into the pitfalls (which can happy in any language/ecosystem).

There's nothing wrong with choosing PHP, and also nothing wrong with other alternatives too.

    "Deep in the browser’s privacy settings, Firefox introduced an experimental “privacy-preserving ad measurement” toggle, enabling it by default without explanation or disclosure."

This isn't even the first time Firefox has collaborated with an ad or marketing company, rolled out a feature behind a checkbox that users didn't know about, turned it on by default. See the case of the 'Alternate Reality Game' ad campaign for Mr Robot a few years ago: https://news.ycombinator.com/item?id=15940144

I stopped hearing when Mozilla talks about privacy or caring about users. Most companies that treat their users like Mozilla just do it, but it actually adds insult to injury that Mozilla tells you they care, tells you you're important while they do the same things. It's gaslighting or manipulation or lying or something but I'm not going to listen to them any more.

Can you explain why it should never be used, beyond subjective preference?

Perhaps it was because of his top priorities, which were: "Developers, developers, developers, developers!"

I love bluetooth headphones for listening to video or even talking, but it has too much latency for realtime music performance (e.g. music making apps, or using your phone as a MIDI instrument with a controller). Having the wired headphone jack without the latency that (any) wireless protocol necessarily introduces is a huge deadlbreaking feature and I never see people defending bluetooth headsets mention it.

Excellent website! Thanks for sharing, I learned something: the scientific name of a cheetah.

Tell your daughter to keep making things that she likes to make!

It looks like you didn't read all the way to the end, and custom data attributes can be for whatever you desire. Presently a lot of people are putting style information right in class names so this distinction you're speaking about isn't present now and developers are already violating it in a big way. The solution in the article is at least using tag names, attributes, and attribute values in ways they're meant to be used. There's a warning about abusing class names in the CSS spec that reads like this:

    Note: Because CSS gives considerable power to the "class" attribute, authors could conceivably design their own "document language" based on elements with almost no associated presentation (such as div and span in HTML) and assigning style information through the "class" attribute. Authors should avoid this practice since the structural elements of a document language often have recognized and accepted meanings and author-defined classes may not.

https://www.w3.org/TR/selectors-4/#example-f9c08b5b