Not "subtly getting a minor detail wrong", but "doing something that is explicitly mentioned as not allowed" levels of wrong.
1,071 karma · joined January 10, 2010
Not "subtly getting a minor detail wrong", but "doing something that is explicitly mentioned as not allowed" levels of wrong.
Have you read the GDPR, though? Because in no way does it require "cookie consent", incidentally, neither did the previous "cookie law". The consent forms I've seen so far are all willfull misinterpretation, dark patterns, or both.
95% (if not more) of non-shady uses of cookies do not require consent, and thus don't need a consent popup. If you do implement one on your website it means one of several things:
1) You did not actually read or understand when/why you need consent
2) You did read it/don't understand, but are unable to figure out where all the stuff on your site is actually coming from and are thus unsure about the implications
3) You actually need consent (in case you are hosed anyway, you can't predicate usage on consent, so there's 0 motivation for users to ever consent)
4) Your purposely trying to annoy EU residents in hopes they will lobby against GDPR back in the EU
5) You're blindly copying what other people are doing, because thinking is hard.
thousands upon thousands of hours of unpaid manual labour...
The design is often (intentionally) tricky to navigate. Brick/cobble roads to make driving fast uncomfortable. Planter's narrowing/blocking half the road, resulting in the road frequently being limited to a single lane (often alternating sides) so cars can't simultaneously pass. Frequent 90 degree turns, that sorta thing. It make it impossible to drive fast on these roads.
Note that this is only applied in some "zones", generally this applies to streets with houses, which will then connect up to a 30 km/h max road that is less obstructed and functions as a connecting artery to main roads in the city/town and eventually provincial roads (80 km/h) or highways.
Each classification has different goals, so highways and provincial roads are "vehicles only", cyclists and pedestrians will be on completely separate unconnected paths (usually with several meters of separation from the main road).
Main roads will have both cars and cyclists, but usually separate/designated bike lanes (and sometimes even separated bike paths). Only the 30km/h and woonerf streets really have bikes and cars mixed on the same lane (and will have measures that restrict car speed like I mentioned above).
But the filter for multiples of 3 only sees the values that weren't already filtered by 2. So if we have N filters we don't evaluate all N filters for each value. The 2 is applied to everything, the 3 filter is only applied to things that are not multiples of 2, the 5 filter is only applied to things that aren't multiple of 2 and 3, etc. That doesn't sound very quadratic to me.
That's not really true, though, because that filter is applied lazily, so it only get evaluated up until the Nth prime and no further.
The time complexity is less obvious, each prime adds an additional pass to evaluate, so that seems linear, but each new pass only applies to a list that already had all the previous passes filtered out, so that's not technically linear, but I find it hard to determine how much it actually is.
I've been using Mercurial nearly exclusively for interacting with git/github since, well, forever. The only case that breaks for me is git repos with submodules, which is the only reason I haven't been able to completely avoid git.
This is just false, the old bash is GPL2 and Apple publishes the source for their bash on their open source compliance page. The reason they don't upgrade is the GPL3 patent grant clause, they ship the last GPL2 release for all GNU utils. The linux kernel is GPL2, so Microsoft doesn't have this problem.
If we assume Hask, the universe of Haskell types and functions operating, is a category (which is hotly debated with some regularity, as there is no formal definition of Hask). Then the Functor class in Haskell really only describes one specific subset of functors: endofunctors on Hask (i.e. mapping objects (types) in Hask to objects in Hask).
This is a rather limited subset of all functors. You can also see this in the laws for example. You probably know the 2 functor laws "fmap id x = id x" and "fmap f . fmap g = fmap (f . g)", but Haskell's Functor is limited enough that these are actually redundant. In Haskell having a proof of just 1 functor law gives you the other one for free (as a free theorem, Wadler's "Theorems for Free!" is a good intro, and another paper. It basically covers "why is more generic code easier to reason about").
> The resource I am reading on category theory makes it seem highly relevant to Haskell and software design in general.
I'm not saying there aren't some useful ideas to be gleaned at both the superficial and deeper levels. The whole lawfulness of functors is great for being able to reason about code without knowing what it actually does, and all of lens is deeply inspired by category theory.
All of CT is about composition and reasoning about it, which we could certainly use more of in programming. So I encourage anyone curious to look into. I'm just trying to provide some nuance to the...enthusiastic overhyping of CT, because I don't want people to be scared away of wonderful tools and languages like Haskell, just because they think they're not smart enough to get all that fuzzy math :)
- Type theory (Benjamin Pierce's "Types and Programming Languages" is the de facto introduction to this. It covers everything from untyped lambda calculus to things way more complex than standard Haskell, including example implementations of type checker, etc.)
- Computer assisted proofs/formal verification of programs (the Software Foundations book series, co-authored by Pierce are a good (and free!) intro: https://softwarefoundations.cis.upenn.edu/)
- The Spineless Tagless G-machine (if you are a more low level/C minded person, this talks about how we compile a lazy functiona language like Haskell to an Intel CPU: http://citeseer.ist.psu.edu/viewdoc/summary?doi=10.1.1.53.37...)
- The Typeclassopedia (which talks about how various CT inspired classes relate to each other and their laws: https://wiki.haskell.org/Typeclassopedia)
I would consider myself a fairly expert Haskell programmer and I have (for fun/curiousity) spend some time reading up on/studying category theory and I can say, without a doubt or hesitation that if your goal is to either 1) understand Haskell better and/or 2) become better at writing Haskell, then studying category is a MAJOR waste of your time. I would advise you to spend that time instead on reading up on the lambda calculus, type theory, and some basic algebra (like this post).
Haskell is not/has never been based on category theory (and I keep being baffled by how many people on social media will claim that it is, given how well documented it's origins are) and the common terminology of Functor/Monad that have been pilfered from CT via Wadler have only a passing resemblance/relation to their CT friends.
Some things that I instead would recommend reading up on are: - Type theory (Benjamin Pierce's "Types and Programming Languages" is the de facto introduction to this. It covers everything from untyped lambda calculus to things way more complex than standard Haskell, including example implementations of type checker, etc.) - Computer assisted proofs/formal verification of programs (the Software Foundations book series, co-authored by Pierce are a good (and free!) intro: https://softwarefoundations.cis.upenn.edu/) - The Spineless Tagless G-machine (if you are a more low level/C minded person, this talks about how we compile a lazy functiona language like Haskell to an Intel CPU: http://citeseer.ist.psu.edu/viewdoc/summary?doi=10.1.1.53.37...) - The Typeclassopedia (which talks about how various CT inspired classes relate to each other and their laws: https://wiki.haskell.org/Typeclassopedia)
EDIT: All of the above is not to say that you shouldn't learn category theory, but that you should have realistic reasons/expectations (even if that reason is just "I'm curious and it's cool"). I just hate seeing people get burned out trying to "get" category theory and (as a result) deciding Haskell must not be for them...
High energy dogs get bored, frustrated, or destructive when not given enough exercise. And a high intelligence just means they're that much more creative in finding ways to amuse themselves (that probably won't amuse you...).
Additionally, part of what makes dogs such amazing companions is their empathy for humans not just intelligence. The current dog of my aunt and uncle is pretty dumb, compared to the previous one. But he loves people, cuddling, and he's super mellow.
He still needs to be walked 3-4 times a day, but not particularly long and he's perfectly happy just chilling and lying next to you all Saturday. That fits much better into less active lives than something high energy that needs to run 10-15 miles a day...
Keep in mind that they're 12+ and travelling in groups of 10 to 20 kids. Kidnapping a group that big is...not easy :)
They are, if you run into them and they feel threatened (especially mothers with babes). But it's super rare to run into them, as they avoid people. A group of teens out at night staying quiet enough to stumble across one seems infinitesimally small. Which is probably why I don't ever remember ever hearing of anyone attacked by boars...
On the other hand, we do (technically) have mountains, as Saba has Mount Scenery (887m) and Sint Eustatius has The Quill ( 601m)...
For me a "good tool" is robust, reliable, and easy to fix. For most of the data scientists I know, a "good tool" is one where "a single easy to remember command magically does the thing I want in one go".
And I get it, that last part is super appealing, especially for people who care more about answers to their problem than in technology, I don't blame people for wanting that.
But my personal experience is that many of these magical single command tools break a lot when you try to use them in any non-standard environment (for example, something that is not Ubuntu and where you don't have sudo to fix/install system packages) and I work in environments like that a lot. So the fact that e.g. cabal-install requires a bit more explicit work to setup initially is outweighed by the fact that I can reliably install it on any *nix system where I have a login and sufficient diskspace and have it Just Work.
Without monads? Not pretty far, but they're far simpler than the wide web would have you believe.
Without category theory? Sky's the limit. I say this as experienced Haskell programmer occasionally dabbling in category theory for funsies. The practical impact on "how easy is it to program Haskell" of category theory is basically zero.
Not even that, the "cookie law" is grossly misunderstood, since it already allowed things like "session cookies" and other account related settings/preferences without any sort of banner. What it banned/didn't allow (at least not without warning) is 3rd party/ad tracking cookies. Some companies just added blanket warnings "to be safe", everyone started mimicing that and now we have the insanity that is modern web publishing...
Since the author of Dhall comes from the Haskell community, he's kept this style.
Like all things "It Depends (TM)", I wouldn't worry about it. Since the introduction of the bachelor/master system here more people have stopped after getting their bachelor, but the "default" in much of continental Europe for technical degrees (as far as I can tell) is still to finish a master.
All my friends and colleagues with masters and PhDs in CS seem to have 0 issue finding jobs or getting contacted by Google/Facebook/Amazon recruiters. So worrying about it being a negative signal seems like a waste of time.
FYI, "allowing EU users to opt-out" is still wrong, they would have to explicitly opt-in to targeted ads. At least, in so far as ads are targeted based on personal data.
For the record, your EU representative isn't required to be a lawyer or even legal expert, though.
Showing third party ads without consent is perfectly fine. IFF you don't gather, share, or process any personal data in doing so. If they serve static non-personalised ads, that's perfectly GDPR compliant.