dtrailin

Unless it's a 1 for 1 replica I don't see how it's a substitute in the copyright sense.

Chroma runs on Windows since I believe it's just a python package: https://github.com/chroma-core/chroma

Having a waitlist was a smart approach for Bluesky. Gives them an opportunity to scale and polish the user experience while building hype for people without an invite.

Interesting, so your argument is not about parroting but specifically about the novel code Copilot generates. My sense is that it would be fine for all licenses except for AGPL as this is an online service and is not "distributed" per say. That is if you don't buy the argument that machine learning is a transformative work so it doesn't matter what the license is, which is the position of current US caselaw.

It's not clear why it would need to be if it runs as a online service. I would say this is analogous to a search engine index. Google for example likely has lots of GPL code in it's index in some transformed form and yet there is little dispute that this is legal.

There some interesting writing from Joel Spolsky on these types of FAQs : https://www.joelonsoftware.com/2018/04/23/strange-and-madden...

When Jeff and I were talking about the initial design of Stack Overflow, I told him about this popular Usenet group for the C programming language in the 1980s. It was called comp.lang.c.

C is a simple and limited programming language. You can get a C compiler that fits in 100K. So, when you make a discussion group about C, you quickly run out of things to talk about.

Also. In the 1990s, C was a common language for undergraduates who were learning programming. And, in fact, said undergraduates would have very basic problems in C. And they might show up on comp.lang.c asking their questions.

And the old-timers on comp.lang.c were bored. So bored. Bored of the undergraduates showing up every September wondering why they can’t return a local char array from a function et cetera, et cetera, ad nauseum. Every damn September.

The old timers invented the concept of FAQs. They used them to say “please don’t ask things that have been asked before, ever, in the history of Usenet” which honestly meant that the only questions they really wanted to see were so bizarre and so esoteric that they were really enormously boring to 99% of working C programmers. The newsgroup languished because it catered only to the few people that had been there for a decade.

The modern equivalent would probably be sorting StackOverflow questions by votes.

How does this feature work on Gitlab? Can you link a doc? Is it VS code as well?

I would bet on AWS in this case as they will also likely have the support of anyone who wants to make a hosted service of those products. It will be interesting to see if eventually AWS starts making new APIs that diverge from the Elastic or if they chose to keep the product maintenance mode.

Where can I see a list of DMCA requests that Gitlab has received and which ones Gitlab has chosen not to comply with?

It's also not that uncommon to see people go from Amazon go to Microsoft especially in teams like Azure. There's more difference between teams within the two of them than there is between the two as a whole. Although, people generally go to Microsoft for better work life balance and benefits. Going from Microsoft to Amazon to boomerang back to Microsoft is also quite common.

source: work at MS

For me the thorny ethical issue is not so much working on directly evil stuff like missile targeting software for the military but software that has both military and civilian use. For example, consider a company that develops and RTOS that is used in both cars and missiles, where does that stand morally? Even the most benign technology can be used for evil so it's worth asking the question to what culpability individual bear for who their company sells their software to. In the case of SpaceX, I’m sure much of the code is the same between the military and the NASA use cases.

Ensuring that people are using the latest version might become easier if the framework becomes unbundled from the OS. I bet every Chromebook and Chromecast is using the latest Android version.

I wonder if we will reach a point where Android might become the standard way to make apps across every platform. The framework seem abstract enough that it seems like run on different kernels (e.g. fuchsia). Would be interesting to see a native Android implementation on Mac and Windows.

Would be interested in what that salary range is. I assume a larger part of their comp is RSU and options.

Given current 50x multiples and high valuations for unprofitable tech companies I don't think there is much evidence that that current stock markets are unable to value long term ventures. As well the extent to which a company is expected to deliver quarterly results is more defined by their board and capital structure than anything in inherent to NYSE or the NASDAQ.

Yes, this seems very similar to the ONNX Runtime https://github.com/microsoft/onnxruntime. I'm not sure why they needed to reinvent the wheel here.

I don't think any of these companies are going "full remote". It seems like the strategy is more like, remote if you want it but there is still an office.

This sounds similar to BuildXL[1] (originally called Domino) which Microsoft uses to build Windows has been in use 6 years. It does this sandboxing using Detours on Windows which intercepts system calls and allows you to described packages in a language called DScript. I think you need something like this if you don't use a system like Bazel that keeps build dependencies well isolated. Even then the system you use can leak into the build.

1. https://github.com/microsoft/BuildXL

200k is fairly normal if not low for a senior backed role in SF. Especially considering that any stock options you got would end up being worthless.

Basically every big corp uses always on VPNs and it works fine. You can even do stuff over group policy on Windows to get the VPN configured and auto join enabled.

Lots of those that build on the Twitter platform gets burned at some point. They have shown not themselves to be a reliable partner. Any company doing social media management at some point gets hurt by changing APIs and increasing fees, sometimes causing fatal damage to their business.

The most harmful idea he introduced is stack ranking, the consequences of which we're still dealing with in the tech industry. In particular ranking people on a team level on the team and firing those on the bottom has taken a severe toll on many teams and companies/

Members of the current or two most recent YCombinator batches (currently s2019, w2018, and s2018)

That requirement is a pretty substantial difference.

(disclosure: I work for MS)

This was the most shocking for me. How is Blind getting my FB info from the app? Is there a way to prevent this on Android?

I think generally scrolling is less smooth than in the old edge. That was one thing they got right and hopefully we'll see improvements in this area upstream in chromium.

Rust is not the right choice because it's trendy, but because it provides memory and thread safety properties that are hard to enforce in C++. For systems software the advantages are huge.

I'm really surprised this isn't in Rust considering security is a priority. However, I think something like this will become increasingly common for high performance cloud applications. Many programs do not need a full operating system with processes isolation and hardware drivers if they're going to run alone on a VM anyways.

Having worked at Bloomberg I really wish there was more content published about how it's implemented because it pretty astonishing in both good and bad ways. For one thing the codebase is ancient there are still some Fortran bits that in use today. However the more modern code is in C/C++ and designed heavily with latency in mind. In particular the feeds are designed to be extremely fast with a few custom built high performance databases built to serve this [0].

The bit that really amazed me was the way the front end is implemented. The front-end is fully rendered server side (meaning every click requires a full round trip to Bloombergs servers) in Javascript using spidermonkey. This caused a lot of difficulties since any real time elements needed to be rendered in a totally different way. As well the version of Javascript was restricted from using things like timers or callbacks since that could make rendering stall. In some ways it's impressive that they were doing server side Javascript at least 5 years before nodeJS but whole approach seems like a byproduct of age of mainframes.

[0] https://bloomberg.github.io/comdb2/overview_home.html

These reports behind an email wall frustrate me to no end. I don't want to receive your spam to read a single article!

A very clever thing they're doing is conflating being an employee with not having flexible hours, as if part time jobs don't exist. Fast food chains don't hire independent contractors and yet lots of people have flexible shifts.