Oh, this is cool! I've actually been thinking for a while that things like Helm or CloudFormation templates or other infra-as-code things would be better served by something like Starlark, but Lua probably suits as well.
I think so. It definitely seems like a nice shortcut to link together adjacent concepts and queries. If a page talking about a particular topic (but in a different way or with different phrasing) than the original page it could help build out a kind of list of related topics.
Of course, left to their own devices and granted the opportunity, kids will naturally do the thing they most want to do and it never appears to be anything of consequence until you look back on it many years from now.
I'm sure my Mum thought I was just wasting time on the computer at 8, but I'm where I am today because of it. But this is equivalent to me having reverse engineered and coded a commercial piece of software that I began in high school... that never happened, and I loved programming.
For what it's worth, mostly private CAs are garbage. Bad at the crypto parts, bad at the identity problem, bad at their own security. Just pretty bad.
It doesn't really matter, because mostly bad guys don't see the CA as the weak point, if anything what is remarkable about the Web PKI is that we did a good enough job elsewhere that actual bad guys sometimes try to attack the Web PKI. Not often, but it happens at all.
It's like finding out you did a good enough job securing your home that an actual burglar picked your front door lock! Yes, the burglar still got in because of course no door look is effective against somebody who knows what they're doing and has plenty of time to try - but still, apparently you actually did a good enough job that they weren't able to just climb in through a side window or force open a patio door. Go you.
If STIR/SHAKEN turns out to have the CA function as its weak point then everybody involved should clap themselves on the back for an extraordinarily good job.
It doesn't go into a lot of detail, but I think they already have a drugs-like classification system for firearms, with delegated authority to decide what goes in what category, so they're just moving all semi-auto to the "banned" category.
That’s the same type of reporting I’ve seen everywhere. “New Zealand bans guns” — can a single PM even do that? Is there any debate in their parliament regarding the move? Do citizens have the same constitutional protections there as they do here w.r.t. gun ownership?
It’s almost like the headlines are written in such a way as to say “See? It’s just that easy!”
It is so nice to come on HN and get some relief from the monotonous humorlessness that is life in USA today. For a moment, I imagine that I can laugh at funny statements no matter which way they point politically, rather than restricting my entertainment to grumbling in approved ways about whomever we're supposed to despise now.
Yes. I've tried implementing some of these on my wife's laptop after using them myself for some time and not having any problems. Then quickly learned that the sites she comes across while browsing are far far more likely to break with these tools than the sites that I (a computer geek) visit.
I've had to dial it back significantly. Disconnect is the only blocker that has passed the wife test. I originally discounted it because the UI for dealing with breakage is worse than Privacy Badger or Ghostery (The default UI doesn't list blocked conent, the graph is harder to see host names at a glance, and the button to temporarily disable all blocking is not as obvious). But the fact that it is more conservative in what it blocks to begin with makes up for it. I still wouldn't enable it for people I don't live with though.
I was also shocked at how frequently HTTPS Everywhere breaks things. I stopped using that myself (and I use uMatrix, with stricter than default base rules).
I'm testing out Decentraleyes right now. It claims to be 100% non-breaking, and so far that appears to be the case. The problem it is addressing (tracking browsing habits via JS libraries) isn't one of the biggest privacy concerns out there, but if it doesn't break anything, and decreases bandwidth to boot, why not!
But...they will be able to write DSLs in it. Just create functions with the same name as the head atom of the top level lists, then run the config file as a program. Or write macros matching the syntax of your format to generate code.
I mean, maybe there is something about your format that makes these specific approachs inconvenient. But once you give a Lisper a bunch of S-expressions, you just opened the door for them to unleash the full power of Lisp upon it.
So I think your plan to frustrate Lispers by making an S-expression based format popular, will just give them even more power.
I once saw a large party of school children going on a trip on the Caltrain. Turned out they weren't going anywhere... it was just going on the train that was the activity. A commuter train running alongside a highway through urban sprawl. They were whooping when it pulled into the station.
> The gun reform proposal will be introduced to Parliament in the first week of April. For it to come into effect, lawmakers need to vote on amending the existing legislation, the Arms Act 1983.
> In the interim, New Zealand Governor General Patsy Reddy has signed an order to reclassify some semi-automatic weapons as "military-style".
> As a result, many people who legally owned certain firearms will no longer be able to possess them on their existing license conditions.
So, a bit of both. The Government can make some immediate changes; others require Parliament's involvement in the near future. (Presumably there's an agreement already largely worked out there.)
I mean you can represent any code as an AST that you can easily write down in YAML, the “programming” isn’t happening in YAML though but by the program interpreting/compiling it. Ansible could’ve used JSON instead of YAML to the same effect, it’s just that YAML is more readable and easier to write (in their opinion).
I'm in agreeance here. Using bitcoin takes away a lot of financial tools. The Federal Reserve has a purpose and a responsibility, using bitcoin would send us backwards not forwards.
Further, the native population was far higher pro Brexit.
As for misinformation, I don't know any Brexiters who were voting based on Boris Johnson's obviously politically gamed claims from someone who is a Brexiter purely for political reasons (I don't think the population is as naive as you give them credit for, and presuming Brexiters to be stupid is BS fallacy), but on the basis that the EU is not properly democratically accountable and the Brit economic/business attitude and politics is not compatible with European ways (ie, high State control). We want to go back to a low paper-work, low-bureaucracy, liberally-inclined environment. Brexit is a start.
I have lived a significant proportion of my life in Europe, and the UK is not meaningfully European. It should have never have been a member, and has been a problem to the EU ever since. It should have been consulted on joining the EU at the very least, and it was not. Now that it has had 20 years of the EU, a 52% vote against remaining is significant.
I think there’s so much that can be automated that isn’t, in every team I’ve worked in. Almost everything other than non repetitive / creative processes (design, coding, exploratory testing) should ideally be automated.
The reason it doesn’t happen most of the time is because other than automating tests, where the benefit is super obvious, there’s no role or job assigned for automating stuff specifically. It’s usually done as part of another job, such as someone responsible for SRE. Automation doesn’t mean it’s set and forget, it needs maintenance, updating, as processes change. People often automate once, realise the process has changed, deem the automation a failure or useless now, and because things need to work right away (to take care of other deli erivables understandably) they don’t update the automation program but rather continue doing things manually because of the instant success of achieving it manually.
Automation takes upfront investment but the idea is it pays off over the long term. If people think processes are going to keep changing and the automation system is not flexible to deal with that it won’t happen. It needs a dedicated person to do this and maintain this in larger teams.
You also need to figure out a way to demonstrate the value of you having taken the time to automate something, especially if your management/leadership isn’t clear on it. Shameless plug, I work on Tesults (https://www.tesults.com) for reporting test results, and even though the primary aim of it is not to demonstrate the value of automation it is definitely a byproduct/side-effect, customers have said this.
Personally I’d focused on the obvious first: tests, build processes such as getting code from repos for building, release artifact output. For mobile apps for example have ipa and apk files automatically available for download by manual testers. Then go onto less obvious things like automated sprint creation for upcoming sprints in JIRA etc with their API. If in marketing, perhaps social media automation for things their apis allow.
This whole argument pivots on the idea that you don't need code in your data.
Sure, you should wrap up all the shell commands you plan to use into code fragments that you can reference. It's neater that way. Suddenly, you have 50 beautifully unit tested objects in your code, each encapsulating a different way you planned on using 'grep'.
And then you open-source your tool, and hundreds of people descend on it and yearn to use it in ways unimaginable to you. You then have to decide whether you're going to a) create a plugin system that allows nicely tested modules in whatever language the user is most familiar with, b) you wrap all the functions yourself (good luck!), c) Say "Sorry, my beautiful tool - with is 99% exactly what you need - is totally not for this. Fork it and be gone" - or d) let people embed scripting statements or shell commands in some way.
If you have the time for (a) and (b), and this is the issue on which you wish to sacrifice yourself, more power to you. If (c) makes more sense to you, then thank you for your input, sorry your project didn't quite take off like you planned.
But please, don't get upset if people choose (d) and get on with their lives. Yes, it _might_ cause pain further down the road, but it's their road to travel.
You could prefix this to every HN thread in existence.
React-Router is reasonably good, and has some issues - like most open source libraries.