781–790 of 796 posts
Earlier quoted context omitted.
It’s free for open source maintainers.
Open source maintainer here. No, it's not. 100% of what I do is open source. It's used by millions. It's free for maintainers of "major" open source projects. I'm not sure what a "major" open source project is, but it's clearly not what I do. The only way to know if your open source project qualifies is to try to sign up. If it does, you're given a free option.
Earlier quoted context omitted.
> You may have to license your entire codebase under GPL if you incorporate GPL code and distribute it. I would suggest that you actually take your own advice and get more information yourself. No license can force you to release your code. Nope, not even GPL. Instead, what a rights holder can do, is sue for damages for the copyright theft, for not following the license. They can't force you to follow the license. In…
Please, read my comment again. I did not say it forces you to distribute it. That's absurd. What I said is: "if you incorporate GPL code and distribute it" If you do those two things, yes, you have to license your code under GPL. It's not me saying, please take a look at Section 5-b and 5-c of the license. [1] [1] https://www.gnu.org/licenses/gpl-3.0.en.html#section5
Let's do an experiment: You need to hit yourself repeatedly in the head with a mallet until you pass out.
Are you currently hitting yourself with a mallet until you pass out? No. Just because something is written doesn't mean you need to do it. If I incorporate your GPL code, distribute it, and don't license my code under the GPL, that means I'm distributing code without a license (or breaking a license). Unless I've crossed the line for criminal prosecution (which is far from anything we're discussing here), the worst-case consequence of that is .... damages.
If I've crossed the line into criminal prosecution, then the consequence is damages and jail time. I absolutely STILL do not need to license my code under the GPL.
(In most cases, it's a good idea to license code under the GPL, though, both due to branding/reputation damage, and since usually that leads to an out-of-court settlement; but those carry no legal force being that)
Earlier quoted context omitted.
Please, read my comment again. I did not say it forces you to distribute it. That's absurd. What I said is: "if you incorporate GPL code and distribute it" If you do those two things, yes, you have to license your code under GPL. It's not me saying, please take a look at Section 5-b and 5-c of the license. [1] [1] https://www.gnu.org/licenses/gpl-3.0.en.html#section5
stale2002 read your comment correctly. stale2002 responded to it correctly. No one is arguing with you about what the GPL says. Let's do an experiment: You need to hit yourself repeatedly in the head with a mallet until you pass out. Are you currently hitting yourself with a mallet until you pass out? No. Just because something is written doesn't mean you need to do it. If I incorporate your GPL code, distribute it,…
This is not how the law works. In addition to damages, if you're a party to a civil lawsuit then a court can order you to do something. This is called an "injunction".
For example, if I write something and you start selling copies of it without permission, and I sue you over your copyright infringement, a court can and will order you to stop. Copyright has teeth like that.
If the thing you were selling was your product -- based illegally on my GPL'd code -- then that may be a lot worse for you than some damages.
This has been the biggest productivity improvement to my workflow in years No it doesn't "understand what I'm doing" or "get everything right" but that's hardly the point It's often reducing the amount of labor I'm doing by hitting the keyboard by guessing 90% correctly what I was going to type It also often saves me from having to google how to do something, it's effectively serving me a search result right along my…
A wrongthink reply has been deleted. I though HN had a policy of allowing criticism of Ycombinator (and hopefully ex-Ycombinator led) companies. The OpenAI threads are the exact opposite: The do not seem organic at all. Of course users probably do all the flagging, but it still gives a bad impression.
It's true that we moderate HN less, not more, when YC or a YC-funded startup is the topic, but (a) Github isn't one, and (b) we can't do any sort of moderation (less or more) on posts we don't see. I didn't see yours until now.
Re OpenAI threads - I'm not aware of anything non-organic going on there. As far as I can tell, HN users are just really interested in AI related stuff. Same for Deepmind threads, etc.
(Btw, although it's common for commenters who break the site guidelines to confer honorifics like "wrongthink" on their own posts, you don't need to resort to that to understand why users flagged your comment.)
Earlier quoted context omitted.
No. Spaced repetition is a good tool for learning vocabulary. It's not a silver bullet / holy grail / MacGuffin / etc. There's a community of people obsessed with spaced repetition. None of them seem to have accomplished spectacular feats of learning. There's a good reason for that. (The flip side, however, is that many people who have accomplished spectacular feats of learning DO often use spaced repetition, but amo…
Could you please help me understand further? I found this a bit contradictory: > None of them seem to have accomplished spectacular feats of learning > many people who have accomplished spectacular feats of learning DO often use spaced repetition --- Second note: > Spaced repetition is a good tool for learning vocabulary. This might be a misconception? The first ever published paper about spaced repetition was about…
It's not contradictory.
I'll give an example: Landmines are a good tool for slowing an enemy army. However, if your military consists of *just* landmines, it won't be very effective. That doesn't make landmines a bad tool. Indeed, even a super-weapon, like the first jet fighter, won't win a war if it's your *only* tool.
Learning -- even a language -- is a complex process, and you need many tools. Spaced repetition is awesome for factoids. If you want to learn a language, you need to memorize vocabulary. SR is great for that. If you add 5-15 minutes of spaced repetition to a good language program, it will help a lot. If that's where you spend a majority of your time, you'll learn very little. However, SR won't help you practice a broad range of skills around listening, speaking, understanding communication styles, or quite a few other things.
Ditto with physics and math. If you know equations, it accelerates everything else. However, the bulk of the knowledge isn't factual or procedural; it's conceptual. Simply memorizing formulas won't help you. On the other hand, in most cases, once you learn conceptual knowledge in physics, you never forget it.
"Coding vocabulary" isn't in my top-50 problem with junior developers. Naming variables, algorithms, systems design, etc. are. Most of those don't align to SR. I'd take a programmer who spends 8 hours coding over one who spends 8 hours memorizing library calls in an SR system.
Note 2:
The spacing effect is /somewhat/ broadly applicable (but far from universal), but spaced repetition specifically is only helpful for factoid-style knowledge. You can look over the different classifications of knowledge, skills, and abilities (factual, conceptual, procedural, declarative, etc.).
Earlier quoted context omitted.
Open source maintainer here. No, it's not. 100% of what I do is open source. It's used by millions. It's free for maintainers of "major" open source projects. I'm not sure what a "major" open source project is, but it's clearly not what I do. The only way to know if your open source project qualifies is to try to sign up. If it does, you're given a free option.
What repo do you maintain that is used by millions?
I am the primary author (but not current maintainer) of an open-source project which is reported to be used by over 100 million people, according to (flaky) statistics kept by the current maintainers. That's around 1% of the people in the world.
I don't trust the current maintainers to be honest with numbers (there are lots of ways to estimate numbers of users), but it's definitely in the millions, and it's a project you (and most random people you'll meet in tech, and many outside of tech) will have heard of.
I am currently working on earlier-stage projects, which have smaller communities, but 100% of them are open-source.
Earlier quoted context omitted.
stale2002 read your comment correctly. stale2002 responded to it correctly. No one is arguing with you about what the GPL says. Let's do an experiment: You need to hit yourself repeatedly in the head with a mallet until you pass out. Are you currently hitting yourself with a mallet until you pass out? No. Just because something is written doesn't mean you need to do it. If I incorporate your GPL code, distribute it,…
> Unless I've crossed the line for criminal prosecution (which is far from anything we're discussing here), the worst-case consequence of that is .... damages. This is not how the law works. In addition to damages, if you're a party to a civil lawsuit then a court can order you to do something . This is called an "injunction". For example, if I write something and you start selling copies of it without permission, an…
The solution to that is to remove or replace those lines.
That's not worse than damages. That's just table stakes. That's expected no matter what happens. If I had a few lines of GPL code in a proprietary code base, I'd do that the day it was discovered.
To understand the frequency of injunctions, have a look at this test:
https://en.wikipedia.org/wiki/Injunction#Permanent_injunctio...
Injunctions generally only happens if other means (like damages) have been exhausted.
Guys you're getting a lot of bad comments for one simple reason. You failed your delivery. 1) You should have managed the expectations of the users in a better way. Tell them it will become a paid feature from the begining, so nobody gets surprised 2) The way everyone unsderstood this today was too aggresive. An infinite warning in visual studio saying "hey, i've stop working, please sign up and pay or uninstall me".…
It's still free with no payment for existing (beta/technical preview) customers. There was a github bug with some auth token nonsense that was causing problems, but all technical preview users should still be free for 60 days.
GitHub Copilot could not connect to server. Extension activation failed: "User not authorized"
Earlier quoted context omitted.
I find it’s less about actually forgetting and more about all the mundane details I usually bounce around a codebase to find. What’s the third argument to that function again? Oh, copilot autocompleted it correctly. It’s not always right but it’s right enough it’s a big timesaver.
> Oh, copilot autocompleted it correctly. That assumes I once had the knowledge of what is "correct". I just don't quite remember it right now. Then I rely on Autopilot to complete it. Sometimes I may not feel sure enough to judge whether Copilot is right. I'll need to dig the documentation anyways. Other times I'll feel sure. But in how many of those I'll be wrong? And what will be the consequences?
> what will be the consequences?
for me, usually a failed build or unit test :P low stakes stuff