645 karma · joined December 16, 2018
Constitutional amendments are hard to pass. That doesn't mean they ought to be.
I/the poster is claiming small states should be allowed to be "bullied" by larger states since smaller states have less people, and thus, are less important.
Unlike other monopolies (telecom, defense contracting) etc. where the monopoly is used to stagnate innovation (see Comcast being terrible), here the monopoly leads to more innovation. Smaller companies can't embark on Google-sized projects.
Sidenote: I'm pretty sure this lawsuit is just a political attack. It seems reasonable that other monopolies in healthcare/defense/etc. are much much worse, yet they aren't "liberal"/"blue" companies, so there are no lawsuits.
Disclosure: I'm interning at Google. I don't think this matters at all, but someone called me out on this in the comments.
Software developers want to know whether their existing marketing methods are effective. The FB SDK helps with this. You always have the choice to not install the app (if you don't want to).
This also helps developers make sure their marketing is effective and reaching the right people, which seems like a win-win to me.
Example from Typescript:
const foo: 'A' | 'B' | 'C' = 'A'
Which states that foo must belong to the given union type. How would this look in a Type ident language?
const 'A' | 'B' | 'C' foo
That doesn't seem right. There's no clear barrier between the type and the identifier name.
Here's another contrived example:
const foo: () => Promise<void> = async (x) => console.log(x)
Here foo is of type "() => Promise<void>". How would this look in a Type ident language?
const () => Promise<void> foo = async (x) => console.log(x)
To me, this is unclear because it is hard to tell where the type ends and the actual function begins.
Last example.
const foo: { [string]: number} = {"hello": 3}
I believe says that foo is an object with string keys and number values.
What does this look like in a Type ident language?
const { [string]: number} foo = {"hello": 3}
I think all of the Type ident examples are more confusing because it's to tell where the type ends and the name begins (this is most clear in the first example). This probably makes syntax highlighting worse/parsing more complicated/is tougher on the user. With ident: Type, it is very clear that the type starts after the ":" and ends before the "=" sign.
There's a bunch of very complex web/electron apps that disprove the idea that the web is only for static documentation and web-inspired ideas are coming to mobile (React --> Jetpack Compose/Swift UI).
More importantly, hiring can't be put aside, and it's much easier to adapt your web app to work for mobile (since websites should be screen size agnostic anyway) than it is to build a fully native app from scratch.
Then again, I'm working at Google this summer, so maybe I'm biased ...
Obviously the sorting algorithim you use matters, so this post has some theoretical value.
The need to save the planet is more important than a person's desire to have kids.
I don't say this out of negativity for the sake of negativity. Earlier today, I was trying to resurrect an old Python project that was using pipenv.
"pipenv install" gave me an error about accepting 1 argument, but 3 were provided.
Then I switched to Poetry. Poetry kept on detecting my Python2 installation, but not my Python3 installation. It seemed like I had to use pyenv, which I didn't want to use, since that's another tool to use and setup on different machines.
I gave up and started rewriting the project (web scraper) in Node.js with Puppeteer.
I think FB has added more to the world (wealth, high tech jobs, open source technology, places for people to organize, ways for people to connect) than it has taken away in the form of FB addiction and manipulative ads.
The masses have always had their bread and circuses. I don't see why a new digital variation is any worse than existing forms of mindless entertainment.
And yes, Electron isn't simple. No one cares. The product itself is simple to use (presumably). When they said simple, they were not referring to implementation details.
Not serving ICE is a more legitimate moral judgement because ICE has the option to change their behavior and ICE is genuinely bad.
Slippery slope is one of those silly things I see from free speech advocates. I tend not to see the bad impacts in real life because if the government isgoing to restrict free speech, they will do it regardless of what anti-hate speech laws currently exist.
I'm inclined to believe them compared to some random stranger who asserts that it should be easy for Mercurial to be ported to Python 3.
Unless you were saying that most other/non-Mercurial programs are easy to port to Python 3, which could be true.