PaulCarrack
One of my favorite videos (and songs) sang by Bobby: https://www.youtube.com/watch?v=9w3yoIOK-9U (Eat Your Vegetables)
RIP. You will be missed Bobby.
You can easily accumulate hundreds of unique email addresses this way.
Do they really expect you to input 500+ email addresses?
Galen is a super smart guy, but he's not a decision maker. I have yet to hear that this is actually the official direction Microsoft as a whole is taking, across any of their business segments.
Why would you pay someone to do something you enjoy doing, so you don't have to do (any/some/all) of it? What kind of side projects are we talking about here?
The biggest issue are AI generated PR slop that takes time to process. Not this kind of "I'd like to make a PR in the future" kind of thing.
@spagoop can you reupload it?
I don't think anyone would be against Woz stepping into to revitalize Apple. The real question is whether Woz would do it.
Had a similar situation happen with another company. Went to take them to small claims but the judge threw it out because of the arbitration clause. We then spent months and many resources but were unable to continue because we couldn't successfully contact their arbitrator to proceed with the dispute. Long story short, we wrote it all off as it was becoming too expensive both with time and resources.
This is all by design, and admittedly, a clever way for companies to do what they do.
In the end, it's the users that end up suffering. The guy (Hocko) kept making mistake after mistake and Kent struggled to get him to do anything remotely net positive with regard to the issues in that original thread.
I'm not arguing that what Kent did was right or wrong, but I would be curious to hear what other ways people work with remote developers who are awful, especially when they work for other companies. You can't just fire them, so I understand the frustration here.
How do they get official parts that need to be replaced on the watch? Rolex is super tight supply chain wise about their parts for this very reason that they want you to keep everything in house. So I suppose they are replacing parts on the watch with aftermarket?
Do you have a source for this? I was not under the impression that this was the case. I know they won't service any watch that's been altered or modified from factory specs.
Assuming a Rolex gets stolen and reported as stolen, it can never be serviced by any reputable watch repair shop because it will be confiscated once that happens. In the case of Rolex, they will get serviced BY Rolex. Mechanical watches do need servicing otherwise they wont function properly. So even though watches cannot be tracked to the same level of fidelity as say, a phone with an antenna, it will likely still pop up eventually.
You can also make the argument that "Find My" and "activation locks" type stuff just means that the parts are going to get scrapped and sold. That could likely happen in the watch case too, so those features were never a silver bullet.
These days on HN, anytime I see a post about Sourcegraph my knee jerk reaction is to whince because I know it's probably not a good thing.
It will be a sad day for tech when they get rid of the on prem free version. I feel like that's the next logical thing to cut given the direction and momentum they are heading.
I would love to contribute and pay, but, as a single personal / private onprem user, it's impossible. It's $49 per user with a 50 user minimum.
Sourcegraph doesn't make it possible to contribute in that circumstance.
In the past, I've found actual bugs that I reported to Justin Dorfman and worked with him to get those bugs assigned to the right engineers so they got fixed before your enterprise customers can experience them.
1. Is there still a path for reporting issues now that the repo has gone private? The Github issue tracker can no longer be accessed or searched through to report bugs or figure out if a bug is known or being worked on.
2. Do you plan to get rid of "Sourcegraph Free" for on premise personal use?
By announcements you are referring to broadcasts which are limited to the broadcast domain of whatever IP the ISP has assigned you. Plus those are largely blocked by the ISP beyond that.
So to say that you are broadcasting to the world that you have an SMB share available is not true. An attacker would have to scan for it (i.e. make an active connection to TCP port 445 on your machine).