I want bash scripts, but with conveniences and lightweight dependencies that can be inlined.
Imagine a "direnv-like" standard library of functions, alongside the ability to fetch-if-not-installed certain binaries, and maybe even a super simple module system.
Then, you bake the script, and it becomes a single file bash script.
To be clear, I want to write it in bash, and have it turn into "bash that I can curl".
Pretty shure this would require either a derivative language [i.e. "enhanced bash" / "ebash"] or require some preprocessor approach like #Blitz [#BASIC] and #Sass [#TypeScript]...
Hi, as a #FunctionalProgramming beginner, I'd appreciate any guidance. Links to in-depth discussion, examples, and summaries would be great. I'm pretty fine with #JavaScript overall, and have used some FP features, but strict FP is new to me.
Note to self: #Calckey is really cool! Must remember to brush up on #TypeScript, download and install the #code, and start tweaking. Start with investigating why some users cannot be followed on Calckey. Something to do with older Misskey servers. Oh GOD! This just one of my gajillion unfinished projects. When am I ever going to finish them? Maybe one day, when I die, many projects will still be unfinished. I'm always a work in progress, and need not despair. 🥲
I built a magnifier with @TauriApps, @vite, #vue and #typescript called "Milky Warp" 🌌! I'm doing a few presentations for http://roller-coaster.app, and I noticed it's not easy to read text on a screen or a small video. I couldn't find a good magnifier tool, so I built one!
Of course, I didn't want to go through the hassle of setting up a C++ project with some weird shaders, so I decided to go with the awesome #Tauri. Milky Warp is open source, you can give it a look, or follow this thread for a few technical explanations.
"TypeScript sucked out much of the joy I had writing JavaScript. I’m forever grateful that @yukihiro_matz didn’t succumb to the pressure of adding similar type hints to Ruby. May we forever enjoy this beloved language without 🙏"
@woodsbythesea As a web dev I still use both, js for simple stuff on generally static sites. But, I absolutely use TS for anything web-app-ish. I would never want to refactor a web app in JS, that's like "break stuff and move slow".
Not using TS because it's occasionally unwieldly is the same as not using AI because it occasionally makes a mistake. #typescript#types#javascript
I'm including in my project an abstraction layer for data access so that when I inevitably feel the need to switch to a different library (or database!), the code I'll need to change will be contained.
One option I'd tried was TS first, but couldn't represent all the column/indexing/FK relationships.
It's an interesting route, and I didn't see much projects that would move away from #TypeScript to #JSDoc type hints. I tried writing generics in it some months ago and didn't find this experience pleasing at all. But I hope this doesn't serve as a limitation for making #Svelte type-safe.
@below Hate is a strong a word! #typescript has it's usecases!
If you for example have a project that could be realized with one developer in 1 month but you have 3 developers that need work just tell the client that your team uses typescript and that it costs 3 developers for 3 month.
So I learned to embrace #typescript in my company 😉
We are a small fully remote team and we offer very flexible #remote working conditions on high-quality business applications for people who love #Angular and #TypeScript but may need a break from big corporations and over-demanding agencies.
I think #Typescript needs to be described as a programming language for describing types that generates error messages which are often helpful, sometimes perplexing, and occasionally make you want to set fire to something, rather than a “superset of Javascript” (which it most definitely is not*).
(* Want an example? Javascript has true private class properties.)
This week on my #livecoding stream with @jitterted, we discuss estimation, responding to dealine pressure, academic studies, and more. Oh, and our tests find a bug that only #nullables could expose!
This is the final episode of the season, but we'll be back in two weeks with an interesting new problem: a natural-language role-playing game. We'll be using #TypeScript + #React with a #Java + #SpringBoot back end to integrate with #ChatGPT. Should be super interesting.
That starts in two weeks—the livestream is May 8th from 1-4pm Pacific, and the recording will go up on May 12th. Calendar reminder here:
Was C++ always super annoying to work with, or did I just grow dumber with age? Was Visual Studio always so fragile and error-prone, or did I just get used to good IDEs?
Confusingly, VS Code seems massively better than Visual Studio. Intellisense handling for TypeScript in VSCode seems so much more stable than it does for C++ in VS.
Wasn't VS supposed to be an upgrade from VSCode?
Wasn't C++ supposed to be more type-safe than TypeScript?