4,271 karma · joined September 4, 2007
[ my public key: https://keybase.io/ketralnis; my proof: https://keybase.io/ketralnis/sigs/-b8hg9xv4sLOgAEnBoAfmQjftzv790I-mM2YelSrYfI ]
For context on why, python's in-built re library is a backtracking regex implementation (as are most) but google's re2 uses a DFA-based system instead that just doesn't support the kinds of regexes that catastrophically backtrack (well, re2 can can fall back to its NFA approach instead which can handle the same kinds of backtracking regexes that re can, but this fallback can be disabled.)
It's also incidentally quite a lot faster for many of the common cases. I swapped re->re2 for an internal rules engine relying heavily on regexes that needed to be robust to novice users and got roughly twice the performance out of it as a happy side effect. For my purposes it was fully drop-in, just swapping out some imports. The only downside was that the regexes that I was explicitly choosing not to support anymore now errored out as intended (and the users that wrote them were given workarounds but not lookarounds :)
We can and should improve development practises, mitigate vulnerabities (ASLR, WAFs, etc), isolate systems from each other, and model threats in a way that we know where and how to do those things. It's not easy but just moaning "everything sucks" isn't how to fix it.
To me this isn't nuanced at all. It's my fucking car, get out of here with this rent-seeking DLC shit.
A researcher could have bought their own copy of the lock and picked it there. Or even borrowed yours with some notice, or let you know so you could have them use an interior door instead, or any number of other things that didn't break your actual house.
"Oh okay it's just non-citizens" "oh okay it's just criminals" "oh okay it's just people that have been arrested" "oh okay it's just people about to go through the TSA but they don't store it" "oh okay they do store it but they take real good care of it" ...
You can look back at some things that occured and say "well it's because it's easy" or whatever, but to be rigourous you'd have to also apply that to the languages that _didn't_ win, and the reasons that they didn't win to Python, and at best there's loose correlation.
This is the same as people that point to "why" billionaires are billionaires. There's a whole lot of luck to it that you can't discount.
Further, I'd question the premise. It's clearly the first thing that people reach for in ML and in the top 3 for web backends. But it hasn't always been that way and it won't always be. Programmers have way too much ADD and contrarianism for any such state of affairs to last for long. And in other spaces and even in other social circles it would be unheard of.
I don't know what you want us to say here. If you don't like it then you don't like it. No skin off of anybody's teeth if egypturnash isn't convinced.
Want to keep running that old package? Cross an ubuntu versioning chasm and now you also need an ancient version of glibc which won't run on your Zany Zamboni fleet because your other requirement of libxml 5 won't work with it. Find a security problem? Well there's a newer version that's only been out for four minutes why aren't you on that already anyway? Oh we don't publish packages for your 4 week old npm yarn bower neonode, who still uses that?
In this particular case you're also looking "closer" at an interaction than you can model with the particle intuition. For simple electron/photon scattering you can pretend that things are particles and use that intuition to guide you but when you start looking really close at things you can't really do that anymore and have to work with fields and waves in a way that belies normal physical intuition. Part of the way that manifests is "virtual particles" popping in and out of existence (really field interactions that aren't really particle-like but with the virtual particle trick can be modelled almost as if they were). These interactions do affect the real world and the way they affect it depends on the fields involved. If there's some unknown 4th generation of lepton for instance a virtual one of those could interact with the experiment, but since you didn't know about it you didn't include it in your calculation.
Also depending on how you're calculating things you aren't just saying "1+2=3", you're saying "1±theory error + 2±theory error = 3±theory error" so you end up with a range of calculations. That might manifest as "well if there's a graviton then I need to calculate it this way but if there isn't then I need to calculate it this way, and we don't have experimental evidence to guide me one way or the other".
Lastly, QFT is quantum mechanics + special relativity and I think it goes without saying that both of these are just detailed, difficult fields with difficult maths involved. So you're taking an already difficult field and since you're trying to be accurate out to a lot of decimal places while interacting with messy real-world experiments you're forgoing all of the nice physics-class "massless particle in a spherical box" approximations that normally let you skip over all of that trouble.
See https://indico.fnal.gov/event/7309/contributions/101335/atta... for some lecture notes on the base problem.
0: https://en.wikipedia.org/wiki/Path_integral_formulation 1: https://en.wikipedia.org/wiki/Feynman_diagram 2: https://en.wikipedia.org/wiki/Effective_field_theory 3: https://en.wikipedia.org/wiki/Renormalization
Sadly “move on” today means moving to a single vendor’s walled garden. We don’t really have truly federated protocols anymore. We do have some contenders but none that my mother and barber and government use.
- Since Apple is currently charging 30%, another app store might charge only 10% and so you might be able to get your spotify subscription for 20% less.
- A provider of especially expensive software (say a CAD or Mathematica) might be unwilling to cede so much of their margin to anybody at all and may prefer to run their own single-item "store", making them the only place to get that particular item.
- Same for especially inexpensive software. Open source game ports that don't want to pay Apple's developer fees. They may make so little margin, including 0, that they aren't feasible with Apple's tax. New software may become sustainable to develop and distribute that isn't currently.
- Porn. Emulators. Anything that doesn't conform to Apple's capricious reviewers. Software that does conform but the pain of dealing with Apple made them give up. The kinds of things that are available on the jailbroken appstores currently.
I'm glad you personally don't have a need for any of these things but that's hardly evidence that the market for it shouldn't be allowed to exist.
But I don't think that's representative. "Or just stop working" isn't a valid alternative to the rest of the world. Outside of mobile ecosystems and maybe web development most things aren't on these 6 to 12 month update cycles. It would be absolutely unreasonable to tell a hospital that every piece of hardware and software and MRI machine in their building has to be upgraded every 2 years or it's positively geriatric and do you even `pacman -Syyu` bro?
Theres a whole world of things that haven't been, and may never be, transitioned. Useful things like utility control computers and even peoples' 10 year old, still perfectly functional and supported desktops. Heck, my "end user" newly-installed fibre ISP doesn't support IPv6! And their previous DSL installation to the same address did! So much for "solved problem" :(
Sure, yeah. That's how price increases work. Nobody's arguing that it's not a price increase. But if your delivered pizza's costs are fuel+ingredients and the price of fuel goes up, well, the whole price goes up or you have to give on the amount of pizza. The price of the ingredients didn't go down, so yeah you're just going to have to pay more or get less pizza. Sorry.
You can quibble on the pizzeria's margin I guess: AWS could just eat the increased price themselves, and probably have been until now. But apparently they don't want to so they're raising the price to compensate in frankly the most reasonable way possible. AWS has insane pricing for many of its services, especially bandwidth, but this isn't one of them.
It's not hidden, they put it right up on their blog https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address... the opening line of which is "We are introducing a new charge for public IPv4 addresses" and when it starts and what the cost is. I assume like every other AWS charge it's broken out in great detail on their billing statements and even have APIs to query costs. Usually they send an email with these changes too so if they haven't I assume they will. It's a regular old price hike but it's not a hidden one.
Secondly since "the cost to acquire a single public IPv4 address has risen more than 300% over the past 5 years", there's no accompanying decrease in server costs that would be "reasonable" to account for this. Charging for the IP itself makes total sense since that's the cost they're accounting for. If it were packed into the instance costs, then instances without a public IP would be paying for it too. This incentivises you to do exactly what they want you to do: use fewer public IPs where you don't need them. This is way more reasonable than an across-the-board instance cost bump which would be a hidden price hike. This is a bridge toll that covers the cost of the bridge by its users instead of raising taxes on everyone.
I guess you're wanting to pay the same and just distribute the cost between the IP and the instance differently? And hey me too, I love not being charged more. But they want to account for their costs without eating into their margin and this is how they're going about it. You don't have to like it; I sure don't. You can wish AWS would just keep eating the cost for you; me too! But I don't think "hidden" or "unreasonable" is accurate.
You can tell because this is a right-wing government trying to do this while Communism and Marxism are left-wing ideologies.
I also have a corner store that loves to get my coins. I suspect he has to make awkward change more often than a big-box store does because when I pull out my $3 in quarters before breaking out the paper bills he always thanks me for it
It's hard to secure encryption keys. If you had a backdoor based on a key that you had to keep secret, leaks like these can happen. If Microsoft (or anyone) can't keep their encryption keys secure, they'd be equally unable to keep a backdoor key secure for the same reason.
If I were pitching in to renovate a property I'd want equity in it. You can do that with or without the inheritance or the prenup: figure out the value of the property before and after the renovations and assign that percentage to the person that covered them.
That's what I'd do in a non-romantic housemate situation but of course a marriage is way more complicated and there are lots of pieces that aren't purely legal or equity in nature. A prenup isn't going to absolve you of that.