somishere

More likely biodiversity will reduce in the north and key species will simply begin moving south

I used to appreciate PHP, I just don't have a use for it anymore.

mmm.. to be fair, I think you're making the point for them. Also, I would be of the opinion that browsers provide a more common runtime than node.

No doubt. Any number of c-levels I have worked with are prolific climbers whose numero uno skill is Network. Lords of LinkedIn. The kind of people who will say and do literally anything to keep their fingernails dug deep. Their actions appear to align with the needs of a company, so most are tolerated if not celebrated.

I quite enjoy minisearch[1] which is also 0 dependencies, actively maintained, and I expect would work well in a worker environment. I dropped it into a service worker and plugged it with a simple point in polygon script to enable geosearch for a recent project[2] and it played v. nicely.

[1] https://github.com/lucaong/minisearch

[2] https://github.com/theprojectsomething/re.places

I'm doing exactly this for my mum at the moment. Trialing various apps and methods. Best so far has been polycam (tho only with photos, hers is an older iphone) uploaded to sketchfab for embed .. that said I think we're content with not shooting the bottom of the various pieces, so they are presented on a table or a wheel. Good luck!

Really like stackblitz.That said, I happen to be working on it at the moment (in FF104) and have been having a bunch of issues (as of very recently).

Biggest one is that I had to disable Enhanced Tracking Protection to get the preview to work. Only a new relic analytics script was listed in the panel, but reading further I found ETP probably still presents other gotchas for their container setup (see below).

More of an annoyance, but I'm also getting "Service workers are disabled by Firefox on this page[...]" message logged persistently to the console, with a link[1] that goes some way to explaining the ETP issue above. Everything still works. In fact, the log appears to be associated with a firebase service worker, as the subsequent message (every time) is an error due to a firebase long poll getting blocked for CORP header issues.

I'd add that it was working perfectly last week, possibly prior to a browser update. They seem to be somewhat aware of the issue (see [1] and per instructions printed to the non-working preview panel).

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1668408

Can't find a lot of info about this. Is it desktop support only that's been dropped?

Thanks for the explanation/link, appreciate it. I'll reserve my cynicism of using this as a reasoning to hold-up progress.

you've got to break a few eggs..

Seriously tho it seems like a pretty major feature to be introducing. Why not do it right? Surely the complexity should be concealed rather than out front being dealt with in user space.

I get your point. However it relies on an example that actually requires an unbounded lookeahead. This is where I'm confused. Sure, these ambiguous blocks (I'm not sure how many examples there are other than color:hover) aren't prefixed, but they are conclusively postfixed. So any lookahead required should be easily bounded. Where does the unbounded aspect come into it?

Reposting my earlier painfully phone-typed regex to illustrate the point: https://regex101.com/r/aOc2Pz/1

Edit: I should add that I don't doubt that those involved know what they're talking about. I know nothing of briwser-level CSS parsing. I am certain it is a nightmare. I would really just like a better example to explain the unbounded aspect. Especially when it is being given as the primary excuse to cripple / greatly obtusify a syntax I'm being asked for an opinion on. Maybe it's just me but I would expect that an evolution of this magnitude would afford a bit more compromise elsewhere.

malevolent css targeting non-performant regex .. sounds utterly despicable.

Can you elaborate exactly where the unbounded lookahead is required? I genuinely can't see it. I also don't see why a dramatic update like this couldn't also introduce / require a 'strict' style to be considered valid.

I feel like we're talking serious edge cases here.

I guess I'd just like to see a good example. CSS is fairly process intensive, not to parse, but because it directly effects the render. Surely compiling a sheet with some lookahead magic isn't going to explode anything that you couldn't already explode with a 'will-change'?

Not if you only require strict mode for modern language incantations like nesting

It's a mouthful alright!

The color:hover example seems like a pretty wild edge case. I'd be interested to see a more solid example of a 'boundless' lookahead requirement. In my simplistic view surely a strict mode that requires semicolons after properties (as opposed to commas or curly brackets after selectors) would do the trick?

Edit: I put together (painfully typed out on a phone) an example regex[1] to use the color:hover example. It isn't perfect, but it also isnt boundless.

[1] https://regex101.com/r/aOc2Pz/1

Apologies if I misunderstand, but your "reverse nesting" syntax already works with scss. I.e. `.a{ .b & {}}` => `.b .a {}` ... I'd quite honestly use it fairly often, usually with state/data modifiers on an ancestor (or ancestor sibling!)

Implicit @nest every time for me .. except for example 8 where brackets (finally) made some sense. Also intrigued by the example 9 `&[open]` edge case. Wild.

Honestly tho, I think scss has it right where ampersand is only used for grouping / parenting.

Yes, I was looking for the 'gotcha' when I searched the wiki but none is there. Seriously impressive stat, from a decidedly low-tech yet seemingly still relevant method.

Hey sorry for the delay on this - took a while to find the time. Likely not exactly what you were looking for but hopefully some of the way there: https://gist.github.com/theprojectsomething/a8406ba6be3ed333...

Also posted as a show HN if you had any thoughts :) https://news.ycombinator.com/item?id=32208258

Previous agency hack here of many years (many agencies). Do not take anything communicated to you from businesses like this at face value. Ignore the tone. The Isaac's of this world are not your friend. In fact, they likely personally orchestrated the scenario and tailored the ongoing narrative. I realise how cynical this sounds, but I'm certain your Isaac would agree.

Agencies (and Isaacs) have a place. They are useful for large orgs where certain expectations and business/operating aesthetics are demanded. Agency workflows and billables have evolved specifically for this climate of largesse. Buyer beware.

Source?

Generally speaking, for the vast majority of HN commenters, authoritative statements on the consequences of childbirth for mothers should be taken with a grain of salt .. given as much credence as you would a third-party anecdote from someone who's closest connection to the source material is a daughter, partner, sister or their own mother.

You may be the exception here, but going by the numbers I would expect not.

Lol.

Edit: to be clear, in my experience childbirth (and what comes after) has undeniably lasting, long term consequences for the "donor" / mother. Not to mention the immediate family, broader community, society at large, even the environment. Certainly more so than any organ donation (in my country at least these tend to occur in the moments surrounding death). To me, the parent comment seemed so removed from reality that a lol summed it up :)

I build for Firefox and then bugfix chrome and safari. Safari usually requires a touch of tomfoolery after the fact. But otherwise it's dev butter.

Not quite a hidden tab bar but I modded the TST / FF chrome so only active or recently active tabs show (~3min timer) per personal preference: https://gist.github.com/theprojectsomething/6813b2c27611be03...

While I generally agree with the prevailing sentiment here I actually managed to implement a captive portal with surprisingly little trouble (ubuntu + haproxy). Use case was an offline WLAN where I needed to direct users through a specific flow / landing page. All up it was less than a day's research and work, plus the landing page build.

Found some decent resources in the process such as https://captivebehavior.wballiance.com/

Happy to provide further detail if anyone is interested.

Can confirm this method works surprising well in practice! Most people just get it. I used it with great success to connect people to a WLAN while at sea (and without phone reception / internet to allow googling "what is qr").

That said, it is worth including the password below the QR just in case someone's camera is old or playing up (this happened). I also added an NFC sticker for the tech woke.

I have another method. Let everyone go during covid and then attempt to re-hire them all on less generous terms after the fact. Looking at you DUB (and no doubt many others).

It's possible. I often use vite with multiple build targets (decoupled but with code sharing) .. this can be specified in the rollup config options but my specific build process uses two separate vite configs to resolve some chunking challenges. Everything is parallelised for dev/build in an npm script. From memory there's a bunch of conversations relating to this kind of setup in the GitHub issues.

Edit: vite allows you to specify (e.g. node specific) exclusions/globals in the config, it also allows you to specify a 'library' build if that's what you're interested in .. with named exports, etc.