707 karma · joined December 17, 2013
I found an alternative in the Fediverse, for programming subs, at least: https://programming.dev/
If it works, it works, I guess.
But alas, the motivation is not big enough for me to invest the effort.
Some features I'd like from Neovim are built-in LSP (but Vim has that thank to plugins), and tree-sitter based syntax highlighting.
That's not enough for me to move to Neovim.
I guess the author used "philosophies" because they are mixing pears and apples, so the most specific word that can be stretched enough to encompass those concepts is "philosophy".
- Programming at home as a hobby should never feel like a chore. If you don't feel like programming, just don't. Forcing yourself is only going to make the situation worse.
- Maybe find another hobby. For example, pick up a music instrument. I started practising guitar daily and it does wonders for my mental health. Music, sports, gardening, something that has a "meditative" aspect to it will work. You'll save your "programming energy" for the tasks at work and will enjoy them more.
- If you want to keep on programming on side projects but are hitting a "rut", maybe spice things up with a programming language that is completely alien to what you know. For me Clojure brought new joy a new way of looking at programming and made me fall in love with programming again.
Hope that helps. Also keep in mind this is normal and that we all go through this several times in our careers.
I've seen a talk of yours about Stencil and how it was compatible with other things because of Web-Components.
How is the compatibility of qwik with Web-Components?
Cheers.
The interface looks exactly the same.
If you look for "embedding Gecko", all the documentation seems to be archived/deprecated. It doesn't seem to be supported by Mozilla anymore. And it was never easy.
It matters a lot, especially on mobile phones with less processing power and spotty internet connection.
It's a huge factor, actually. Downloading and parsing React+React-DOM on mobile phones, especially if they are not high end, is miserably slow.
Also, it's not only a user experience problem, your "Google Rank" is influenced by your lighthouse scores.
So I'd argue "that kind of performance" is business critical on several levels. At least in my experience.
- It's completely arbitrary and opaque. - It's irreversible.
With the CSSSS at least you get a notification of what you did, and you can revert it by "behaving".
Also now that I think about it, that might have been a good product test. To see if the tools get out of the way and let the creativity flow.
Well, one known issue was a netsplit [1]. But it did work most of the time.
"If the app can't be in the Play store anymore, there is no point in continuing supporting this app because about 99% of the users download the app from the Play store."
So your employer is the _main reason_ this guy is giving up.
Also you defending your employer in this thread, given the context, is highly insensitive. Makes you look bad, that's why you're getting downvoted.
You should have not commented this, or even better, you should switch to a company that doesn't suck!
That means you have to study the old code, which is of course poorly documented and probably buggy; and then try to reproduce it in a sane way.
We chose it in my company in 2008 before the framework boom and it had served us well for a very long time. It's batteries included, has for example it has a very comprehensive i10n module, which was not usual at the time.
Also worth mentioning it was started among others by Alex Russell [2], a famous developer advocate at Google.
Which maybe I will, because I hate Vimscript.
Booting up is normally not done so often, but also doing other stuff takes way too long for my taste (over the perceivable 300ms threshold).
> Emacs ran on hardware from the 1980’s. How can it be too slow on modern hardware?
Since then they've added millions of lines of ELisp code. The comparison is moot.
Also we are talking here about Emacs "distributions" (Spacemacs, Doom Emacs) which come with a lot of code, and ELisp is not particularly fast.
For example, when I was learning Clojure I used Doom Emacs for a few months, but gave up because:
- Emacs is slow. There's no way around that. It's even slower than VSCode or other IDE-ish editors. If you're used to Vim speeds, that's pretty annoying.
- The Vim keybindings are not available everywhere, for example in some plugins you would fall back to pinky-breaker, wrist punishing Emacs standard keybindings.
- There's some uncanny valley where keybindings are mostly like Vim but you have constantly paper cuts from small differences here and there, among the occasional Emacs-mode fallback.
Don't take me wrong, I can see how Emacs is a great editor, but for me, it's way too late it seems. Seems like I'm going to keep on vimming until the end.
(eg: `margin-left: var(--page-margin);`)
Unit tests have similar advantages to types: they catch errors early and let you refactor your code with confidence.
But unit tests go even further, because they test the _correctness_ of the returned value, not just its type.
And a massive turnoff for me is that the types are compile-time only.
So you see, if your code is tested, and the types are just partial static checks; I feel like it's just not worth it.
I enjoy using types in other languages, for example it feels nice to add type hinting to old PHP codebases. But in PHP, types are much simpler (less work) and more effective.
If they added optional run-time instrumentation like "spec" in Clojure, I would definitely use TS. But for now, I'm out.
Apply it to yourself my friend, you are wrong again. What you are talking about here is implicit type coercion, which doesn't have much to do with strong vs weak types.
Also in your example you do get a warning, so it doesn't seem to be a problem?
> I always think it's hilarious when Clojure enthusiasts try to address concerns about the language by talking about parentheses, as if that was actually the major barrier to entry.
Not that they are a major barrier, but they do scare people away. I know this because I've been tempted to try lisps before and after having a look at some source code, I was "scared" of the parenthesis. They are ugly (at least I thought at first sight) and they seem like very tedious to type. Of course I know better now, but that was _the_ reason I had not to try lispy things, at least on a couple of occasions. So yes, the "the parens are A-OK!" is absolutely warranted when trying to sell Clojure or any lisp for that matter.
> It's slow
So what? If I'm not writing anything CPU bound, I'm not very concerned about that. Clojure is fast enough for most things. The performance penalty is completely justified if it takes me half the time to write an app. This is just a trade off, or do you write all your stuff in ASM?
> Development with the REPL is slow because the startup times are glacial and REPL-oriented development usually requires tons of from-scratch restarts.
This is just very much not true. First of all, nobody is forcing you REPL-oriented programming. Second of all, it doesn't take more than a couple of seconds for most apps to restart. And third, if you use "def" and "defonce" correctly you'll hardly ever have to restart the REPL.
> The tooling sucks.
That's just your opinion, man, and it's also pretty rude. Clojure have awesome IDEs and tooling, and the aforementioned REPL-development allows you to have the same "react-hot-relading" developer experience, anywhere.
> Java interop is a black art.
Java (and Javascript) interop is pretty straight forward. You call functions and instantiate classes and stuff. No naked dancing under the moon involved.
> The ecosystem practically doesn't exist.
It maybe didn't some time ago. The ecosystem right now is thriving with pretty cool projects.
> The lack of static types hurts you in many ways, most of all your ability to refactor with confidence.
That's also pretty subjective, in my opinion the only thing that gives you confidence to refactor is unit testing.
Plus there's other ways to validate parameter and return values in Clojure, and they are not limited to the type.
You'll agree, that a return value is of a given type doesn't guarantee that it's correct.
> Clojurescript is weakly typed, Clojure is strongly typed.
Plain wrong, types are semantically equal in both languages (they are weak). The semantics of the target languages are just implementation details.
You can try this on a REPL of any variant you like:
(def foo 42)
(def foo "Hello, World!")
Sharing code between Clojure and Clojurescript is fine, especially if you stick to the built-in data types and functions. Of course if you have a lot of specific interops interleaved, it's going to be painful.The nocompatible mode means adding some features to vim rendering it "incompatible" with the original vi. For example in the original vi you can only undo the last action, with compatible mode on vim will mimic this behavior.
And you probably should, because vim is rightfully warning you, that you might lose changes made in the other instance.