Mastodon: @sean@dice.camp
It saves ewaste. In 6 years, will macOS still be supported on these machines? Maybe. Will an open source distro be supported? If it’s still thriving, yeah.
I always call my little helper higher order functions (intended to be partially applied) factories :)
deleted by creator
Name one statically typed language that doesn’t have that property. Name one non statically typed language that has that property.
All static typing means is that types don’t change, eg you can’t declare a var as a string and later assign a number to it.
People don’t understand that JIT languages are still compiled, JIT literally describes when it’s compiled.
That said, F# and/or OCaml.
I mean, if the error says “variable foo is not defined” I don’t think it’s wise to go “I’m pretty sure it’s defined, the compiler is just wrong” 😂
I learned early in my software engineering career these two beautiful rules of debugging:
If you have seniority and they are a junior, some juniors do respond well to a senior having more knowledge about the codebase. With them, it can be beneficial to use a tone like “We have library X that seems like it could do a lot of the functionality here, unless you already took a look?” I know it’s like 90% of the same but I know people who will just be shellshocked and just blindly say “yes” to any question you ask them, and I don’t want a blind “yes” I wanna know the truth :) it also lets then explain why they didn’t use it if they have a legit reason because hey, maybe I’m the one who needs to be caught up
Look at gleam and elixir. Both are functional. Both use exceptions, but both also use error values as well. There is no reason why we can’t have both. These are incredibly fault tolerant systems.
People forget that compilers used to be commonly proprietary and commercially licensed. Heck, I’m born on the 90s and knew that 😂
So so glad free and open source software took over though
AGPL? Google has a ban on all AGPL software. Sounds like if you write AGPL software, corporations won’t steal it.
Code licensed under the GNU Affero General Public License (AGPL) MUST NOT be used at Google.
The license places restrictions on software used over a network which are extremely difficult for Google to comply with. Using AGPL software requires that anything it links to must also be licensed under the AGPL. Even if you think you aren’t linking to anything important, it still presents a huge risk to Google because of how integrated much of our code is. The risks heavily outweigh the benefits.
Any FLOSS license that makes a corporation shit its pants like this is good enough to start from IMO.
https://opensource.google/documentation/reference/using/agpl-policy
If it’s only internal then technically the internal users should have access to the source code. Only the people who receive the software get the rights and freedoms of the GPL, no one else.
The one on the right should be labeled “full-stack dev” because that’s like 80% of them and they write in C# and Angular 😂
I wouldn’t say JavaScript is horrible, it’s a fine little language to do general things in if you know JS well. I would say, though, that it is not a great language. Give me F# and I’m happy forever. I do not like typescript that much more than JS.
GitLab isn’t open source, and certainly isn’t an open project first — they have a sales team, a marketing team, and a budget who does not account for getting new dev users
It’s quoting the source who used that specific term
Compile times say otherwise
It really is. I always make a note to point out how much code is removed in PRs I review