740 karma · joined October 14, 2016
It seems rather reasonable to assume that in the goal of maximising privacy in search engines, it would be wise to add user-friendly and convenient features so that the alternative is appealing and does not sacrifice too much convenience.
It would be nice to have this (via regular or template strings) compile to DOM objects, wrapped with a couple of pointers indicating where strings or elements are placed. I guess for now the best course would be to budge that into transpilation, raising an error if it does anything kooky like work at the boundaries of elements.
(.innerHTML setting is sugar for a HTML parser being initialised on the element, so such a transpiler wouldn’t be removing functionality per se)
[1] https://w3c.github.io/DOM-Parsing/#dom-innerhtml-innerhtml
You’re not wrong about clarity; it wouldn’t hurt here at all, but it wouldn’t hinder without, so I imagine it’s to reduce cognitive load and make it abundantly clear the function is logicless glue.
Some user themes are for visual nicety, sure, but they might be essential aids to some. Making it easier to data-grab with BeautifulSoup etc means any data shown is more portable, too. Data scraping is all sorts of useful, and having classes that aren’t minified garble makes it a considerable amount easier to target.
Does that mean we should abandon them? Absolutely not. Encoding phase (or in a much more common subset, parity) is so absolutely useful it’s no wonder we bake 90° intervals (-, i) into our notations: they can be intuitively dealt with. It’s still somewhat easy to skip over the property, however; as a student at least I seem to need to backtrack over signs at least once an hour when working with anything rigorous enough. I wonder if 2-tuple notation, eg (+, 23) or (-i, x²), would be more intuitive by making parity/phase explicit rather than implicit.
Complex numbers are a little more nuanced, but no less useful. I imagine you could develop an alternative notation to make things more intuitive, but thankfully it’s generally taken for given nowadays that they’re intrinsic to how we’ve explored nature.
Businesses don’t have an inherent right to your data. There’s countless bans on much more nefarious practices that “didn’t work” at the time.
That said, the P-spectrum may have some crossover, especially at P1-P2, depending on the release cycle. For example, crashes should be focussed on a little more for always-online software, whereas for more glacial, manually-updated software, prioritising incorrect behaviour or functional issues may be more important.
Not the most useful of features, but it does explain why * is the concat operator.
Plus, y’know, a lot of problems have been solved, so these kind of events provide jobs and boost local and global economies.
It’s not necessarily bad, trying to add a little animation or complexity, if it’s not in-your-face: it can help vary style, experiment with what clicks with an audience, and develop skills. It can also act as a status signal for the website if it can afford for developers to fine-tune every detail – Apple is a good example here.
But yes, the best design is usually one of the simplest ones. Some designers try to make content glide over your eyes and forget that this doesn’t fit usability needs.
That could easily be hydrogen, or even biofuel itself – the ultimate goal is to reduce the carbon cost of storing the energy. While lithium-ion has zero continuous cost, its initial cost is rather high, and if the battery is less efficient or prone to breakage more often its continuous cost (of repair and replacement) may well be worse.
Errors for trivial things (ie control flow) are an unfortunate abuse of try and catch; generally exceptions should only be thrown to users of an external API, not an internal one. If an exception is caught from the same layer of abstraction it was thrown from, it’s a very leaky abstraction — as opposed to, say, a regex parsing error, which ensures the abstraction isn’t implicitly failing.
The best way to make that work in that case would be to explicitly inform the user when unignoring of the conflict and ask which to keep (showing metadata etc). A quick “retain other version” would help if the user was unsure.
>>> display(lightsecond)
>>> v = c / 3
>>> h / electron.mass / v
(3.019×10⁻²⁰ ± 2.277×10⁻²⁸)ls <length, distance>
>>> potrzebie / bushel
62.23m⁻² <vehicle efficiency>
>>> print(f"The speed of light is about {c:.5e}")
The speed of light is about c = 2.99792e+08m·s⁻¹
>>> momentum
mass * length / time
>>> print(flow)
L³·T⁻¹
There's no explicit support for probability, but you can roll your own quick with some support >>> prob = Dimension.new(3.4, "probability", "P", "chance")
>>> chance = Unit(prob)
>>> percent = Unit(chance / 100, "%")
>>> display(percent)
>>> chance / 3
33.33%
[0]: https://github.com/yunruse/noether