I do get that, just saw the "test" op, to either pass or fail the whole change as a sort of transaction. That is really neat.
But I just find that the 1 by 1 approach is easier to reason about if you're opening this up to the internet. I'd personally feel more comfortable with the security model of 1 URL + Session => 1 JSON key.
$WORK project heavily utilizes the test op to enable atomic updates to objects across multiple competing clients. It winds up working really well for that purpose.
NO. A tax is a bad way to regulate any system in the long run. Ideally i would like all telescopes be shifted to outer space. if spacex or its competitor created a orbital satellite network and charged a monthly / yearly fee to get a feed of data from the cost / dollar would far exceed anything available today. tax going to govt is a place for inovation to die.
That is changing with the drone warfare becoming large part of the future wars. US military (and pretty much everyone else) will make drones major focus of advancement and there is definitely lot of money to be made by supplying chips for those.
I didn’t need all the features or complexity of a Mikrotik router so I went simpler. I have a GL.iNet MT-6000. Underneath it runs openwrt and you can access the openwrt luci web interface or ssh to it if you want to do anything more complex than their web ui allows. So far besides enabling sftp so certbot can deploy a ssl cert to replace the default self-signed cert I haven’t needed to.
It also runs AdGuard Home so that is another thing I have been able to remove from my home server.
Thanks, it does look neat, and relatively small I guess, but I should have clarified my definitions.
By small I meant like, at most only a few files in a single folder I can just drop into a project and be off running quickly and easily. Seeing cmake in that repo for example was a big sign that it's still way too big for what I want.
Years ago, someone would say "It is quite easy to write Python code that works just with all Python versions since 2.6. Easier than writing any Perl code..."
Perl requires a 'use version' statement otherwise your code can't use anything added since ~15 years ago. Python has no such system, so it's hard to know if the code is going to work on any given version of python. The core modules also seem to change much more often than Perl's.
All Perl code I have ever seen, has been "write-only". Just completely unreadable and it was easier to just look at the output instead of the code when converting it to Python to get actual maintainability.
You are getting downvoted, but for me, it is the same experience. It's a dead language, and we are switching to Python, that is far better to maintain for me and for all our new hires. I mean, Perl doesn't even has a debugger on Windows.
Not true by any stretch. I've used komodo[1] for more than 2 decades as a debugger in Linux, Mac, and Windows. More recently VSCode on all 3, for debugging.
Definitely not a dead language. A mature and stable language, which won't surprise you.
reply