doc () { curl "https://cheat.sh/$1" | less }
1,111 karma · joined April 11, 2011
I'm mostly Front-End Developer, I do Open Source and I'm also Wikipedia Editor and Blog author.
[ my public key: https://keybase.io/jcubic; my proof: https://keybase.io/jcubic/sigs/SNxeHIzd0GmaQTchY2dLDsnmgTTPHj2rDgnKTMIvRfw ]
doc () { curl "https://cheat.sh/$1" | less }
I've tried to correct the thing and added this:
https://en.wikipedia.org/wiki/Server-side_scripting#Server-s...
I've also reported the issue to some Wiki Project but there where no reply.
But it's really bad because of this: https://en.wikipedia.org/wiki/Web_template_system#Static_sit...
Instead of rant, why not fix Wikipedia and write proper articles for Server Side Generation and Server Side Rendering or whatever is needed.
No one else in the team was doing the same including myself. I'm not exactly sure but maybe part of the reason was that he was not much familiar with the code base, and checking if it works was the way to test if the code is correct.
* Code Reading: The Open Source Perspective
* SICP
https://gist.github.com/jcubic/a8b8c979d200ffde13cc08505f7a6...
The library supports typing animation and changing colors. You can easily create the same interactive console.
If you're interested I can create a demo for this.
For me it's best advice how to start with Open Source, and be sure that your PR will be accepted. And as side effect you will learn a lot, but this is with any practice like with your idea, but you will make project better. Your idea is as worthless as doing LettCode or similar.
Success Open Source project are usually created by very smart and experienced developers. And big projects have a lot of them. Their Code Reviews are much better then anyone your closed source team will have, unless you're junior developer in team of Senior developers.
Right now I'm thinking that at work we also have git (for intranet application) and we have PR, this may be very good idea for newcomers to read the PR that was done to understand how some features were implemented instead of just diving into recent code. This may be best advice I've seen in a while. But maybe it's just my own idea that came from this article, that you've understand differently.
For me this article is about advice read closed PR you will learn a lot, here for Open Source projects, because OSS projects on GitHub are biggest projects you can find.
For me your article is a revelation, didn't realized that I can just read old PR to check how to contribute to Open Source project. I've never read this advice in any guide that show how to contribute to FLOSS and I'm working on Open Source for more than 10 years (I'm sometimes read about how to get started, when I was starting with OSS, there were no guides like this).
I would give this advice to anyone that that want to contribute, it's even more important than looking for good-first-issue or help-wanted. This should be first thing the person do when trying to contribute. Look at old PR.
For me learning new language is side effect. You always learn when you're practicing with real project and work with more experienced developers. It doesn't matter if you work on closed source program in your own team at work or on Open Source. But with Open Source there may be more people, and big project are usually created by very smart people.
A year ago I've read article about the person that self-published a book (printed and ebook), here wrote an article how he do that and how he created it in markdown (very well written book about TypeScript in Polish), I've asked an year ago (when read that article) if can publish the code, he said that he was thinking about this. Recently he published how own blog system online on GitHub and wrote another article this time with link to GitHub. I still waiting for the book code.
The code is on GitHub: https://github.com/jcubic/notes
The app is simple on left there are notes, in the middle there is simple text and on the right are navigation into sections, that are created using special markers. This type of makers I always use in source code and text files as separators.
* https://github.com/jcubic/gps.py
I've also once wrote a tool that downloaded files from shared hosting sites. It was long ago when RapidShare was main site of this type. It was working with all the sites that was available back then and it was waiting before download the file. It was before captcha was invented. I was using router and dynamic IP and I've even added a function that was disconnecting/connecting the router to change IP when download the files.
The code is in Ruby and on GitHub I think this was one of my first project there https://github.com/jcubic/Downloader
* LIPS: https://lips.js.org/ Powerful Scheme-based Lisp interpreter in JavaScript
* jQuery Terminal: https://terminal.jcubic.pl/ for building CLI applications in Browser
* Sysend.js: https://github.com/jcubic/sysend.js for sending messages to other tabs/windows in same browser
* Favloader: https://github.com/jcubic/favloader Favicon animation library
I've also build [sysend.js][2] (random name with send at the end). It's for sending messages between Open Tabs, It have nice API and it works in all modern browsers and even some older ones like IE11. I didn't know any existing library that did the same, that's why I've created one.
Another library of mine is [Tagger][3], because there where no Vanilla JavaScript library like this. I needed it for StackOverflow Q&A site that I've started, but abandoned and it was inspired by StackOverflow tag editor.
Yet another library is [LIPS][4], Powerful Scheme based lisp in JavaScript. LIPS is acronym LIPS Is Pretty Simple (at least it was when I started the project on [Codepen][5]). It started as lisp in JavaScript, but later I decided that I want fully working Scheme (compliant with R5RS and R7RS). I'm still working on Beta 1.0 version, that is like completely new project. I'm also still working on new website that will showcase beta version better.
I've also created [Favloader][7] - favicon animation library. [LILY][8] - Zero dependency, simple version of YARGS for parsing command line arguments.
[0]: https://terminal.jcubic.pl/
[2]: https://github.com/jcubic/sysend.js
[3]: https://github.com/jcubic/tagger
[4]: https://github.com/jcubic/lips
[5]: https://codepen.io/jcubic/pen/gvvzdp
[6]: https://lips.js.org/
Also SEARCH was suppose to be case when you don't mutate data, so SQL insert and update is not good usage of it. You should use POST for that.
Here is advanced example that use real like commands with Pipe operator (from Bash). With figlet, lolcat and cowsay commands that can be mixed: https://codepen.io/jcubic/pen/vYLvvXx
You can glue pretty advanced website just collecting examples from https://terminal.jcubic.pl/examples.php
With jQuery terminal you only need to care about the commands. Note that the library is more like a framework.
What's missing are continuations and proper tail calls. And syntax-rules macros need to be heavy refactored (I need to add proper expansion time).
If you want to take a look make sure to check out 1.0 Beta version, that is completely different than what's suppose to be stable version.
Website: https://lips.js.org/ GitHub: https://github.com/jcubic/lips
The most up to date documentation is on the wiki: https://github.com/jcubic/lips/wiki/v1.0-draft
If you would like to learn on line (maybe using pdf book) you can try my Scheme REPL bookmarklet https://lips.js.org/#bookmark so you don't need to install anything on your computer, you can do that later.
But still I think that `((. console log) "hello")` is not as nice as `(console.log "hello")` as in LIPS. My old code was using the same syntax but I've changed the interpreter and you now can use dot notation on any JavaScript objects.
"Now Go Create"
https://jcubic.github.io/lips/
There is lot of features in devel branch I need to release soon version 0.21.0, but first I need to write unit tests.
was first