Anything’s a regex if you’re brave enough.
Anything’s a regex if you’re brave enough.
Just archive it and take up farming.
No inconvenience—I like these kinds of things but then another question had a typo in it (varx
instead of var x
) and one of the options was ‘Error’ but again that was incorrect. It’s probably worth running these snippets just to make sure :)
Q2: Which is more efficient? Code blocks do 2 different things so cannot compare. What gives?
The graphs are all interactive (touch to show labels, etc.). That can interfere with scrolling—try dragging at the edge or one of the pie chart titles. Fwiw, it scrolls ok on mobile safari…
Same—my local micro brewery does a night once a month where they demo things about brewing. One month they made 6 ales with identical ingredients apart from a different strain of yeast for each. 6 very different drinks.
That’s nearly eleventy thousand. Terrible breach.
I’ve been using AWS R53 for this for ages and it works well. Not specifically recommending AWS but using dynamic updates rather than a DDNS service (or running your own name server which I’ve also done).
It’s a great analysis, and I don’t disagree with anything you said (mostly because you’re better informed than I am). But you nailed it with “Why would I need this? I don’t know yet.” It should all be driven by need—the fact their are more options is great, but doesn’t mean they should be used just because they’re there… For many hobbyists, ease of access and speed to get started is the main driver, and for those cases, pre-built boards are the answer.
I remember talking to a car manufacturer in the early 2000s who said it would be relatively easy to make cars to a custom length / load space. But they tend to make specific models because if you give people too much choice, they get paralysed and don’t choose anything.
I suspect it’s not quite that simple but the principle seems sound.
Just going for cigarettes…
I’m going to get back to watching that later.
Sad Betamax noises
We’ll of course it depends on the scale of the changes. Depending on how your calling them, the version could be in the url, such as zooms api including /v2/ in the urls. Then you can introduce /v3 with many changes whilst leaving /v2 in place for some amount of time.
If /v3 also means a complete change of database and other underlying infrastructure (eg removing the concept of a zoom meeting), then you’ve got different challenges. Those are probably about overall design, not api.
One approach I’ve seen (from a user pov, not dev, so I’ve no idea of the code bloat it might cause) is to pass the API version number in the call. Then your api can be backwards compatible for 2 or 3 versions, giving other users time to upgrade their code. It de-couples things to give you all a bit of slack for both rapid iteration and stability.
But it also depends on the ‘contract’ between you and the users so be very clear how long / how many versions will be available. Probably will involve a ‘use by’ date.
Is there anything looking even remotely promising to replace silicon? Manufacturing base aside, what’s the most like candidate so far?
Find something you’re interested in using yourself. Contributing to multi-dev projects has a whole load of complication over and above single dev projects, and to stay motivated to work through all that whilst also potential learning a new environment will need a good reason to stay involved.
Or volunteers. Don’t know about where you are, but near me, town gardens, flowers, woods and rivers are maintained for all by community-minded volunteer groups.
I remember using Mosaic on Silicon Graohics machines back in the early ‘90s. It’s was fab for the time.
And yes, Mosaic became Netscape, became Firefox. From the wiki page at https://en.m.wikipedia.org/wiki/Netscape_Navigator