Most of Europe, Central and South America, Canada, Australia, Japan, India, South Korea - the majority of the world that could not already be described as authoritarian
Including India in that list is pretty wild
Readit NewsXR0CSWV3h3kZWg commented on Microsoft has urged its employees on H-1B and H-4 visas to return immediately timesofindia.indiatimes.c... · Posted by u/irthomasthomas
XR0CSWV3h3kZWg commented on The Absolute Denial of Shit openspace.sfmoma.org/2018... · Posted by u/thebigship
Adding new stuff to Unicode should have a delay, 20-25 years from proposal to the standard (roughly a generation).
In the meantime it's possible to insert emoji into text as smiley, -smiley-, :) , smiley.jpg, ::smiley:: or whatever you want and the system you use is free to change it into a picture.
We end up with standard that is full of ancient symbols from 2000-2025 and new generations of people will abandon them for something else when the culture changes.
Emoji from 80s:
________
/ "Ship Arriving Too Late to
/ Save a Drowning Witch"
/ /\ F. ZappaMany languages will die before being digitized if they have to wait for 20-25 years
I have been doing some tech advice jobs on the side to see what's going on in the world and it's really scary what I found. Only yesterday I was talking with the cto of a niche social networking company that has a handful of users and probably won't get much more who was telling me the tech they use; Node, Go, Rust, Mongo, Kafka, some graph db I forgot, Redis, Python, React, Graphql, Cassandra, Blockchain (for their voting mechanism...), some document database I had never heard of and a lot more. A massive, brittle, SLOW (!) bag of microservices and technologies tied together where in 'every micro part' they used best practices as dictated by the big winners (Facebook, Google, whatever) in Medium blogs. It was a freak show for a company of 10 engineers. But this is not the first time I encounter it; 3 weeks ago, on the other side of the world, I found a company with about the same 'stack'.
People really drink the koolaid that is written on these sites and it is extremely detrimental to their companies. PostgreSQL with a nice boring Java/.NET layer would blow this stuff out of the water performance wise (for their actual real life usecase), would be far easier to manage, deploy, find people for etc. I mean; using these stacks is good for my wallet as advisor, but I have no clue why people do it when they are not even close to 1/100000th of Facebook.
I saw this at my last company. Even worse breaking it into microservices allowed teams of 2 or 3 to start building entire realms where only they could commit and used it for internal politics.
I witnessed someone that wanted to leverage their service into a promotion so they started pushing for an architecture where everything flowed through their service.
It was the slowest part of our stack and capped at 10tps.
The 'environment' is often in balance. Any abrupt change can cause oscillations and crashes. May as well ask "By not removing this brick from the wall, I may be screwing the wall up!"
Why do you believe that?
XR0CSWV3h3kZWg commented on Anti-If: The missing patterns (2016) code.joejag.com/2016/anti... · Posted by u/fagnerbrack
Just today, I was talking with a team mate about this.
We had some pice of code that it's like this :
public boolean foo() {
if (!this.doesSomethingWithA()) {
return false;
}
if (!this.doesSomethingWithB()) {
return false;
}
if (!this.fooBar2000.isEmpty()) {
return false;
}
if (!this.anotherLongAttribute) {
return false;
}
if (!this.anotherMethod()) {
return false;
}
return true;
}
return !this.doesSomethingWithA()
&& !this.doesSomethingWithB()
&& !this.fooBar2000.isEmpty()
&& !this.anotherLongAttribute
&& !this.anotherMethod();
Yeah the first version looks like something that many people would try to 'optimize' but in reality it is extremely readable and should be very easy to change/extend.
If it benefits others. That’s all I care about.
It seems like tolerating this may not be in the best interest of the community going forward. And I would find it interesting to be able to claim that magic leap has sued me for distributing 3 month old api docs to myself.
> And I would find it interesting to be able to claim that magic leap has sued me for distributing 3 month old api docs to myself.
Do you have that much money to burn?
Nah, I don’t blame the formality. What seems true is that both ipfs and blockchain technologies will make these legal tools obsolete.
What if we were to set up a project in response to this that made the Magic Leap API docs available in a distributed fashion? As well as a technical breakdown of everything that can be learned from them.
Is there no way to disobey in a productive way? Or is our only choice to agree to being bullied into submission for pointless reasons?
> What if we were to set up a project in response to this that made the Magic Leap API docs available in a distributed fashion?
If your name is still attached you will still get these letters. Because they will continue to try and show they are protecting their IP.
> As well as a technical breakdown of everything that can be learned from them.
Then that would be your IP which you'd be free to distribute. You won't receive the same letter again, but you may be breaking an NDA and the terms of which may apply.
Why do you think that ipfs and/or blockchain is going to change how copying IP works?
Not only that, but also an attacker can wait until the money is "safe" outside the exchange before revealing the attack. If the attacker really has more than half of the hash rate, there's no time limit; the malicious chain will always be longer than the innocent one.
In practice there is a time limit. Nodes will not relay blocks that are too far from their current clock.
Yelp exists only because people trust it.
I've only found yelp to be trust worthy in some cities, not universally.
XR0CSWV3h3kZWg commented on UTC Is Enough for Everyone, Right? zachholman.com/talk/utc-i... · Posted by u/bpierre
There is a solution for this, Unix timestamps.
That fails for the case that you have an appointment at 3pm in 30 days, and 15 days later the timezone's offset changed.