1,228 karma · joined December 24, 2012
It is unfortunate that this fear extends to private Russian businesses, but it's difficult to discern how separate entities really are in tightly managed countries.
I totally agree this is getting into some cold-war-era territory though... US vs. Huawei has a similar vibe.
I'm excited to see legislation in this direction but I wish they'd focus on forcing Twitter, Facebook, etc. (which /are/ in California and can be governed) to display / disclose when they are aware a user is likely a bot, and employ some half-decent detection methods.
I'm a big fan of Google watching out for their users. I know of at least one very sketchy company that has shut down because of this new policy, which is great.
But after three months, they basically told me: "Your desktop app makes a network request to a third party server, you must pay $15,000 for a security audit." Their process has been vague and I wish they'd make an effort to understand whether an audit is really necessary. Their security contractors are going to be laughing all the way to the bank as they review my web service that never sees Gmail data in the first place.
Thankfully, Mailspring makes a bit of money and I can afford to do this to keep it alive. But fast-forward a few years and this is going to devastate innovation and development of third party mail clients. (And I think Google prefers it this way.) If the app didn't already have critical mass, or if I was just starting a mail app now, I'd probably throw my hands up and give up rather than emailing them dozens of times and coughing up $15k.
The downside is that Snap-packaged apps don't always integrate correctly with the underlying system. For a while theme support was pretty broken. And subtle configuration options aren't always passed in. Worth it in my case though!
I also feel unit-level tests are less necessary with TypeScript. I used to write a lot of JavaScript tests that essentially just confirmed that "this sh*t is all tied together correctly". With TypeScript, if a code change or refactor broke something structural, you know immediately!
- Does EditorJS support nested blocks? Eg: can I make a list node that contains a list? Can I make a list that contains a blockquote? (DraftJS is a /linear/ set of block elements, making it very difficult to model complex documents - Slate's document model is a tree which is why pretty much why I chose it over DraftJS.)
- Does EditorJS have test coverage? What's the overall testing story look like? I'm not a big TDD person, but we've had a few stability issues with Slate (granted a slightly out of date version) that cause the document state to become invalid after certain edits and then subsequent interactions throw errors. (It's absolutely terrifying to have your text editor crash!)
I'm sure this isn't intended to stop you from running your game's central multiplayer server. It's just to make sure you pay an appropriate licensing fee for Unity.
Maybe the idea is that it feels like a phone, so you pull it from your pocket thanks to extreme smartphone muscle memory. You find your hands have selected a black glass slab that says "PA LM" in the middle, which is quite uninteresting, So you put it away. Distraction crisis averted.
(Kidding obviously, but nothing on the site says otherwise! Honestly I wrote my first mobile app for the Palm V and I would love for this to be a killer rebirth of the Palm brand. Guess we'll have to wait and see though!)
1) You (the early engineer) get promoted and are leading the charge, but have no mentors or role models to help you develop your career.
2) You raise a huge Series A / B, and everyone says "spend it in 18 months" so you hire a ton of people quickly, which significantly changes the company culture. Your first attempts at introducing structure / management to the team are rough, and early engineers get frustrated the growth and seek out smaller teams.
3) You (and everyone else) think the startup is "successful" as valuations increase and build your internal narrative around this success. Later reality sets in - you need a bridge round! Since you and your co-workers placed so much of your self worth in the company's success it totally destroys morale.
This is true, but it's not a feasible approach for software like Slack, Spotify, and VSCode that gets updated /weekly/. These aren't packages like 'libgit' that you could validate once and leave the same until you ship the next OS release. Some of these apps completely stop working if you fall behind by too many versions. Having people running older versions is also a huge pain in the ass as a developer, because those users inevitably email support, complain online about how the product is bad, etc. and only after lots of emailing does it turn out they're using a year-old version. (Full disclosure: I maintain Mailspring and switched to Snapcraft /very/ enthusiastically to have an auto-update mechanism that works across linux distros!)