474 karma · joined December 22, 2015
Because these models work better with more data and presumably this a lot of high quality data that they already have lying around anyway? Because there no downside according to their own reasoning? Because it would shut up a lot of these criticisms right away? Because marketing would be so much easier with that kind of dogfooding?
In short: because according to their own story there would be only upsides, no downsides.
It is the same as what happened with digital photography. In the old days every single publication, no matter how local or modest, that wanted to have a photo to accompany the text needed a photographer. With the invention of digital photography and smartphones, this is no longer the case. Any writer or editor can snap a picture themselves and often it even looks kind of ok.
However, for a real "professional" look and and quality, you still need a skilled expert to take care of the imagery. Because part of providing the image are the mechanics of producing one, but another part is knowing/deciding what the right image is for this occasion. The latter part can only be done by humans for the foreseeable future.
The result is that it is much easier to acquire some picture for you publication, but also there there still is a need for professionals that can do it "proper".
Of course there is something proprietary or original about that. Why else would they need such an enormous AI to suggest it. Auto completing simple boilerplate was already solved in a much simpler way.
> Copyright infringement hasn’t taken place until the user activated the autocompletion and actually placed the code within their own and released their code containing the infringing code.
Copyright infringement takes place as soon as some company publishes/sells material without explicit license or permission. So not the moment the users hits accept, but the moment just before that: when the tool shows it to the user.
Also: polish up your resume and start sending it out.
Meanwhile, I have been blocked from applying for a position multiple times because the online form required me to enter a LinkedIn profile, which I don't have. It would require a lot of time to create a profile and message all my relatives and past co-workers to build a nice looking network.
I just treat this as a sign that we were probably no a good match anyway.
So after I watch that instrumental music video, there will be a mass recommendation for other instrumental music. And that's nice, because I apparently was in a mood for that. And the next day, I open my browser again and they are all gone! I can dive into the music for the mood of that moment right away.
It is not necessarily about power, it is about judgement. However clever or 'smart' the systems we design, there is still a vast gap between what automation can understand and what a human can understand. There are countless examples of a system only doing what it was told to do, where any human with an IQ higher than 80 would immediately recognize that the system is being incredibly dumb and wrong in this particular case.
There needs to be some last resort for the victims of those errors when there are real consequences to these mistakes.
So I went in and... it worked out really well. Quality of life is fantastic, productivity too. It's like we've never done it another way. For the contractors it was even an improvement, because now they were on the same level as the rest. Based on this experience, we have started to hire people from abroad and whoever wants can stay remote.
* Leaves window management to the window manager, so it works much better with a tiling wm. I wish all applications did this.
* Selecting first and then specifying an action works way better than the other way around, as it is done in the Vim family.
Edit: regarding the comments and Vim's visual mode, you are right. I like to change my second bullet to "Does not have too many modes, like the Vim family."
Because buying new stuff is wasteful and only a temporary solution to the problem?
Look, I like nice, fast machine as much as the rest of the crowd here, but let's not kid ourselves. In a years time the software we run on it will have become even more bloated and things will be just as slow as they were. And then a new machine comes out we all want to buy that.
There will be some ecstatic blog posts again. Which is weird, I think. Needing a faster machine for you daily work should feel like defeat for a developer.
If you need a new laptop and can afford it, by all means go ahead and indulge. In the mean time, I am typing this from a 7 year old Latitude that I use every day for software development and that shows no sign of aging, apart from some scratches. And each time I read a post like this I wonder: what do these people _do_ with these machines?
So the Linux subsystem should be called... Linux subsystem. Searching on Google would lead to type "linux subsystem for windows" and it would not be hard for Google to direct you to the right Microsoft website.
No, it isn't.
"I'm not like the normies, because I am cool and underground." is a hipsterism.
"I'm not like the normies, because unlike them I happen to possess the skills to escape from a situation we all hate" is not an hipsterism.
> Linux is the OS for people who like tinkering. Tinkering is the point.
This is also completely false. Improvements were made, things generally work out of the box. Polished and user friendly user interfaces exist.
_But_: interfacing with those commercial products/services that spoiled the fun of mainstream systems generally sucks. Because those only work if you give up control to them. Which was one of the main reasons you went to Linux anyway.
> I almost never look at a candidate's resume/CV. > I don't have time to peruse your GitHub profile or past projects. I don't even have time.
So you want someone you can work with, but you don't want to spend a couple of seconds to look at who you're talking to. Which is, you know, sort of the most basic of things necessary to get an actual relationship started.
This goes both ways. If you don't even want to spend a few minutes to assess whether the resume or the projects are interesting to you, then why on earth would the candidate spare you any time or energy?
I read lists like these, try to understand what the complaint is and then... I realize that I just don't care. There have been two or three occasions in my career that I thought "Man, it would be nice if I could use some generics now", but other than that: I don't give a fuck.
Go is simple enough that I can do whatever I want with it, without holding me back. It is simple enough that I can understand what my colleagues try to do without much effort. It may miss some convenient short cuts, but it is trivial to implement them yourself on the spot.
If it feels therapeutic to write down you annoyances, by all means go ahead. Let it out and get some peace of mind. Other than that: stop whining and just go build something useful with whatever language you prefer.
Not only due to developers. Designers have a hand in this too. Example: on many sites (Twitter, Imgur, etc.), it is not possible to simply zoom in an image without jumping to a lot of hoops. You hover the mouse over the image, the pointer becomes a magnifying glass, you click and...
The image blows up to fill to the screen until it his a overly large and useless border that some daft designer thought looked cute. There is no way to zoom in any further, that is blocked. So zooming to see a part if the image in full detail is out of the question. What's worse, if you have a small screen, likely to be the reason that you wanted to zoom in the first place, the zoomed image is actually smaller than the original. Great!
So, I've wasted my data plan to download a large high resolution image and a bunch of javascript libraries that make sure I don't get to enjoy that resolution. I can't remember for sure, but I bet that his already worked fine in Mosaic in 1994. Not anymore. And why? What benefit does this bring? Other than that it looked nice on the designers computer, I mean.
It does not matter how slice and dice things, the real world is a complex environment and as a result your application will be complex in some way too. You just can't sweep complexity under the carpet and pretend it's not there. It will always come back and bite you, in some way or the other.
I like it that that try to focus on a completely free version, as that is what they stand for and why a lot of people respect them, while at the same time being realistic about the real world problems that people face.
You know what, typing it out I can totally see why people do it the other way. A matter of personal preference probably.
I never understood why people feel the need do this. If you are working on a bug or feature, why put unrelated changes in that branch? It only creates confusion and probably messes up your tests too. And for what? It seems like a chaotic way of working to me.
Yes? That is really not as far fetched as you make it sound. I have no problem paying a creator for something that I enjoy. But I do want to know that its worth the money. In older times we would use the radio to help make that decision. Nowadays there is so much more available than what is played radio, but I still want to make an informed decision. Youtube works well for that too.
Copyright cartels live by bullying. It is not important how much of the takedowns are actually effective, as long as they get to dominate the news with their lawsuits. Because only that will already deter al lot of people. Just drag everything on forever and have an occasional success that you can trump on every news channel. That is enough to spread fear. And that works also in other countries, like The Netherlands, because they will have some representative organization there (Brein, in this case) that is happy to take on the role of the bully for a small amount of cash.
There is no "latest" version of a project in the decentralized model. As soon as there is one "latest" version that rules them all, you have centralized an aspect of the project and that immediately becomes a target for organizations like the RIAA. IPFS does not help here. Because in the end, someone must have the exclusive right to release a new "latest" version. This release mechanism becomes a single point of failure.
Sure, you can use use IPFS to create multiple copies of that new version to avoid having them taken down. But you also could just do `git clone` on a new server, as so many already have done. Creating copies and putting them up for download is not the problem.
If git is used in a true decentralized way, everybody has their own version of the project. No two have to be alike. Do you want to use youtube-dl to download porn, get the version with the right extension. Do you have moral objections to porn, get the version without them. Exactly like there is no "one" Linux, each distro has its own version, with the patches they think are important. This way, the RIAA could even release their own version of the tool. One that can download from Youtube, but not video's that are subject to the copyright they want to uplhold.
Users would not have download the tool directly from that one developer/team, they could download it from whoever they trust to have their best interests at heart. That is what decentralization means.
A lot of people are confused about this because GitHub and GitLab are the only intermediaries they've used to collaborate with git. If that applies to you and you would like to know better, read this: https://drewdevault.com/2019/05/24/What-is-a-fork.html