Visual voicemail
I wonder what happens when an elevator panic!s.
Appreciation for Common Lisp Packages
There are many things to like about Common Lisp packages. In everyday programming, I really like being able to define one or more packages in one file then just have a (in-package package-name) at the top of other files opposed to having sometimes hundreds of lines of imports. Some programming languages are worse than others, but no other programming language that I know of allows one to keep imports in a totally different file.
The real point of this post is to talk about a specific scenario that reveals in interesting interaction between asdf systems (libraries), symbols, and macros. A conversation about packages almost always involves talking about symbols. Here is the situation: there is a library, A, that implements some very useful computations. The public interface for the library is a combination of macros and functions. It is rather verbose though, so you want to wrap it in a macro and create a new library: B. You want the users of your library to only have to use your l
The final strawberry for me was forcing people to have 2fa.
You R a nerd for the last one.
This exact thing happens to me.
JS doesn't do any type inference. Ocaml Connor l type checker knows all the types and is completely type safe without type annotations.
Many farmers growing plants for animal feed. Also there are Deer farms that raise deer specifically for the hunting industry.
I think the bigger problem is that they are hard to write and sometimes break tooling.
I'm pretty sure they operate on tokens not AST.
More modern shirt text would be scheme vs common lisp.
proprietariable just means the code can be taken and rerelased as proprietary (no freedoms all rights reserved).
You can sell GPL licensed software. You don't have to publish the source code publicly online.
You still own the code you release under GPL. the restriction you are describing is actually caused by the non-copyleft licences you claim to prefer. If you choose to use MIT, you are limiting which libraries you can use. If you had picked GPL to begin with, you can use any library.
Copyleft licences are the only true free software licences. All other open source licenses are just proprietariable.
Before cars, people would rice their rice carts.
I know it is an unpopular opinion, but it is a huge headache in general. I don't think the theoretical benefits (which make total sense) actually pay off in reality and are worth the extra headache. I'm not saying they should not have it at all, but it should be at least opt-out instead of forced.
In the case of github, I think it is part of their long drawn out plan of data collection and proprietary lock down. Next they are going to require your house address and government ID. I feel better using an free and open source platform anyway.
I'm just migrating away from github because of this. Sr.ht is looking promising.
Emacs has a proper gui by default. You have to give it option to make it run in the terminal.