infernu
quokka
Our great sponsors
infernu | quokka | |
---|---|---|
2 | 31 | |
337 | 1,167 | |
- | 1.6% | |
0.0 | 1.8 | |
over 5 years ago | over 2 years ago | |
Haskell | ||
GNU General Public License v2.0 only | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
infernu
-
The TypeScript Experience
Or maybe a sound type system can only be achieved either by limiting JavaScript or with a different language that compiles to JavaScript?
-
Features of a dream programming language: 2nd draft.
Very constrained. Since "constraints liberate, liberties constrain", as Bjarnason said. Inspired by Golang's minimalism, and Elm's guardrails. For learnability and maintainability. Since discipline doesn't scale (obligatory xkcd: with too much power, and the wrong nudges, all it takes is a moment of laziness/crunch-time to corrupt a strong foundation), and a complex language affords nerd-sniping kinds of puzzles, and bikeshedding and idiomatic analysis-paralysis. Counter-inspired by Haskell. The virtue of functional programming is that it subtracts features that are too-powerful/footguns (compared to OOP), namely: mutation & side-effects. The language designers should take care of and standardize all the idiomacy (natural modes of expression in the language). "Inside every big ugly language there is a small beautiful language trying to come out." -- sinelaw. The language should assume the developer is an unexperienced, lazy, (immediately) forgetful, and habitual creature. As long as software development is done by mere humans. This assumption sets the bar (the worst case), and is a good principle for DX, as well as UX. The constrained nature of the language should allow for quick learning and proficiency. Complexity should lie in the system and domain, not the language. When the language restricts what can be done, it's easier to understand what was done (a smaller space of possibilities reduces ambiguity and increases predictability, which gives speed for everyone, at a small initial learning cost). The language should avoid Pit of Despair programming, and leave the programmer in the Pit of Success: where its rules encourage you to write correct code in the first place. Inspired by Eric Lippert, but also by Rust.
quokka
-
Quokka Playground - Run JavaScript and TypeScript in VS Code
For more features and details check out the official docs https://quokkajs.com/
- Quokka.js: The JavaScript Playground in Your Editor
-
IDEs vs Text Editors in 2023 for Web Dev: what things have you found full size IDE's like Webstorm can do that VSCode cannot in 2023 which make you more productive? Specially today now that TypeScript + AI coding tools level the playing field even further.
Used to be true, but between Quokka.js for quick prototypes, Wallaby.js for running tests smartly within the IDE, and now Console Ninja which enables inline console.log within the VSCode while running servers for common tooling (webpack, vite). As well as continuously improving collaboration tools like Live Share, And it's become hard for me to find an argument that Webstorm is still better for productivity here.
- SREPL: The file is the REPL
-
I built a tool that let you quickly test JavaScript code suitable for teaching and learning JavaScript
I use https://quokkajs.com/ it has a free version!
-
Use Go in my start-up or stick to TS which I already know?
There are some fantastic tools such as Quokka which make "more algorithmic" development very interactive and fun
-
How to see what the code is doing?
There's also extensions like https://quokkajs.com/
-
Any way to have inline code analysis like this? I believe the Trunk extension does it.
Quokka.js
-
I'd like to use a REPL in my workflow for getting feedback on my code. Is this a reasonable ask? If not, how do you check your code as you go?
I’m a Clojure(script) dev learning TS. My Clojure REPL flow is Cursive + IntelliJ. The closest equivalent I’ve found is https://quokkajs.com for inline evaluation and https://wallabyjs.com for test evaluation. Both are paid products but have free 30 day evaluation periods. Both work in IntelliJ and VsCode.
-
[AskJS] Confused and Struggling
If you want to code and practice your JS in a sandbox, I highly recommend using VS Code (if you're not already using that for your HTML/CSS) in conjunction with Quokka.js. If you use `console.log()` function to log your results, Quokka will output directly in the editor. There are online resources that do something similar like codesandbox.io but I've found it nice to have a local environment.
What are some alternatives?
ascii-art-to-unicode - Small program to convert ASCII box art to Unicode box drawings.
RunJS - RunJS is a JavaScript playground for macOS, Windows and Linux. Write code with instant feedback and access to Node.js and browser APIs.
ekg-carbon - An EKG backend to send statistics to Carbon (part of Graphite monitoring tools)
JS-Interpreter - A sandboxed JavaScript interpreter in JavaScript.
argon2 - Haskell bindings to libargon2 - the reference implementation of the Argon2 password-hashing function
vscode-python - Python extension for Visual Studio Code
gotta-go-fast - A command line utility for practicing typing and measuring your WPM and accuracy.
gtoolkit - Glamorous Toolkit is the Moldable Development environment. It empowers you to make systems explainable through experiences tailored for each problem.
hascard - flashcard TUI with markdown cards
typescript-notebook - Run JavaScript and TypeScript in node.js within VS Code notebooks with excellent support for debugging, tensorflowjs visulizations, plotly, danfojs, etc
aeson-serialize - Functions for serializing a type that is an instance of ToJSON
jupyter - Jupyter metapackage for installation, docs and chat