FIGlet is a computer program, available for many operating systems, for making large letters out of ordinary ASCII text characters
o o o o
| o | / | | o
| OO o-o -o- O--o o-o
| | | \ |-' | | | | \
O---o| o o o-o o o o | o-o _ _
/ \ | \ | T| T Tl j/ ___/
Y Y| D ) | || l | | T( \_
| O || / l_j l_j| _ | | | \__ T
These are my designs/conversions and conversions of other people's designs that I've contributed to the FIGlet archives. They are available to look at here in a sampler and as full FIGlet font files to view or download. I may add more later.
Here is a relatively complete collection of the rest of the contributed and default FIGfonts (actually this is grex's figlet fonts directory, so some of these may not exactly match those in the official FIGlet distribution and contributed fonts collections; I've made a few corrections here and there, or added some characters at the request of grex users). See the main figlet site for the most recent versions of these fonts and any new fonts.
This is the abbreviated FAQ that is posted to the FIGlet mail list periodically. It tells how to subscribe and unsubscribe from the mail list, as well as how to reach the main FIGlet site. This is a local copy.
Here is the link to the main FIGlet site's FAQ document: http://www.figlet.org/faq.html
>o o o o
>| o | / | | o
>| OO o-o -o- O--o o-o
>| | | \ |-' | | | | \
>O---o| o o o-o o o o | o-o
>_ _
>/ \ | \ | T| T Tl j/ ___/
>Y Y| D ) | || l | | T( \_
>| O || / l_j l_j| _ | | | \__ T
>>9
Why do you like JavaScript? I think it's PHP-tier because the lang has so many footguns that it's too easy to make mistakes that are (nearly) impossible in other programming languages.
Like, browsers should come with something like NoScript by default! I think having a blacklist by default would be acceptable behavior. And requiring JS to just show static text is plain evil! These may be web browser issues but browsers are relevant to everything JS because client-side JS is a (huge) thing. Also, there are some issues with the design of JabbaShit. Why are undefined and null different?
There is even a site that has a reasonably good list of bad things in JS (the problem is that the author seems to dislike dynamically typed languages):
https://whydoesitsuck.com/why-does-javascript-suck/
I disagree on the authors conclusion that asm.js is so awesome, though!
- C-like syntax
- native functional features
- sane package/module management for Node.js
- tight integration with web technologies
- TypeScript is an option if static typing is ever needed a fine alternative is to use JSDoc type annotations, they can be checked in modern IDEs as type declarations
I'm not an advocate of heavy JS usage on frontend, but I like to work with Node.js on server-side comparing to other available options.
>the lang has so many footguns that it's too easy to make mistakes that are (nearly) impossible in other programming languages
I think lint won't let it happen in most cases. JavaScript is so popular that its tooling is very decent.
>>11
Oops, I forgot about lints, but it sucks that you are forced to use one. Also, I have only written client-side JavaScript for my personal website. I have never tried Node.js or server-side JS but I think I should. How to get started with it? Any recommended tutorials or books?
I'm not forced to, I use them anyway for any language I work with, for both commercial and pet projects. So what's the hassle?
>How to get started with it? Any recommended tutorials or books?
You already know the basics of JS, aren't you? If not, use this for reference: https://javascript.info
In yes, Node.js is pretty simple to start with, install npm and give it a try. There are docs on Node.js website, I never read any guides, only consulted with man npm, web search and ChatGPT.
Some usual commands:
npm init # start the project
npm install $DEPENDENCY # add a dependency to the project
npm install # install all dependencies
node app.js # run the project, app.js is the standard entry-point
I received a task with mostly Scala programming needed. At first I liked this language, it looked like a hybrid of Haskell and Java, seemingly a good compromise between useful exotics and stable practicality.
However, the more I dive into the real-life code, the more I realize it's ugly, unnecessarily overcomplicated, even bloated, and keeps 30 years of JVM legacy in its very nature.
Finally, OOP is so cumbersome, I have no idea why people think it's somehow beneficial to wrap every piece of shit in a "class". And Scala does seemingly nothing to get away from Javish everything is an object approach.
>>5
Buying monitor couple years ago was the best event in my computer decade and since then I use my current laptop as a desktop workstation 90% of my screen time. It's connected to monitor, mouse, keyboard. So, PC is the option for my computer habits.
Shit, I'm not sure again, maybe, transporting desktop would be fine, in addition to the monitor.
>>6
If you already use your laptop as a desktop workstation 90% of the time, then I would recommend buying a desktop and keeping your old laptop as a backup or something that you can easily access when moving around.
So I guess my response is buy a desktop, keep the old laptop, but the decision ultimately lies on you.
I coded a Node.js web app prototype the whole working day and I think JavaScript is quite comfy.
It's straightforward, has generic syntax you don't need to learn really, and its FP features are killer.
The only downside is actually not the language itself, but NPM bloat. Anyway, it's not worse than, for example, some enterprise standard JVM ecosystem.
HONESTLY JAVASCRIPT ISN'T A BAD LANGUAGE. IF IMPLEMENTED CORRECTLY, IT COULD VERY WELL BE THE BEST LANGUAGE ON EARTH. I BLAME THE STINKY DINKY PAJEETS HONESTLY.
I'm personally not a fan of its overuse on websites. Client-side scripting shouldn't be a thing on websites unless someone's making a web based NES emulator or something, not just loading a microblog with some jpegs attached to it.
>>17
Ideally, I think JavaScript could still be used but only as a last resort or if the benefits significantly outweigh the drawbacks.
I think one reason for it's use is that web devs think about solving the problem in javascript first, rather than think if it can be done with HTML/CSS. This is sometimes seen with navigation bars.
Some bullshit websites could work fine without js, but for some reason require you to use it (ex. openstax.org)
of course the ratwires software doesn't fucking install correctly
how do i install this? seems like all i'd have to do is run make build-dev, make dev, make build and then run the compiled script right? are the first two steps even necessary? the fuck is the development environment anyway?
it's spitting out a ton of errors when i run make dev
but seems like i might not even need to since make build works fine anyway except the bin/ratmachine script doesn't work either
Before you even consider learning to program, you should become skilled in using a computer and just general computer science (ex. make use of command line, networking, etc.)
Then learn programming. You probably hear this a lot, but you will never learn if you don't put in the effort.
Also, I recommend NOT using youtube tutorials, as most will only teach beginner material and are of highly varying quality. I prefer books and occasionally online text-tutorials, but if you prefer videos, then watch them instead, as I'm sure there are high quality ones out there.
I have to recommend sicp, and if you want to go further, there's https://teachyourselfcs.com/ which is basically a full undergraduate curriculum.
However, if you're already set in your career and just want to learn programming to complement it, you should just listen to the other people about python and stuff.
Laziness and thinking ability can be improved over time. Don't underestimate yourself.
For me it's:
- Firefox is default for most WWW consuming needs
- Chromium is secondary, for mostly shitposting under VPN and checking web coding stuff
- Pale Moon exclusively for I2P, proxy is switched on there constantly
Related:
- Thunderbird for reading RSS and Atom feed
>>5
It's sad the Firefox is the only real competitor to chromium.
Although it comes with spyware and bloat out-of-box, you can remove most of it without having to hackerman into the code, which is unlike chromium.
I learned numerous languages and mastered zero. There's always a new shiny language out there.
The last thing I learned was Haskell. Wrote a small CLI app and dropped.
The new language that interests me is OCaml. But I force myself to avoid putting a new shit in my head. For what reason? To learn the basis, maybe, write some dead simple stuff and eventually quit.
I'd like to stick to only one or two languages. How do you achieve this?
A language is a tool. Decide what you want to do, and then pick out the language that works best for your use case.
Your problem is that you're doing the opposite. You're picking a language and then trying to figure out what it's actually useful for (Spoilers: The answer for most functional programming languages is nothing besides intellectual masturbation).
I’d like to add that importance of programming language knowledge is extremely exaggerated on the boards. And the truth is that when you know typical solutions and algorithms, it’s quite easy to pick up a new syntax.
>The answer for most functional programming languages is nothing besides intellectual masturbation
This.
You said “mostly” and that’s correct, because Scala and Erlang are quite usable for niche things. But these enterprise monsters are usually not what kiddos are fascinated with.