Having used evil-mode as my main driver for years, I can confirm that it truly works as expected. Requires some setup though. I used https://github.com/doomemacs/doomemacs to do the heavy lifting though.
Same I love my ligatures to death. And there are some interesting goodies. I find the author take on `tmux` being unecessary interesting, albeit it's a quite divisive opinion. Nevertheless, it's refreshing to see the status quo being challenged.
The delay in between typing and seeing it rendered, drawing large portions of text (which matters if you spend a lot of time in term based editors) etc ...
It's very subjective: some folks (me included) will notice the difference and feel frustrated if it's not fast enough, while others are scratching their head about how it actually makes a difference.
It could also be said, that it's of logical to expect certain things to be fast; especially when they've been around for so long. We're drawing text on the screen here, it should be fast.
Saying it matters with anything else than feeling/comfort would be overreaching.
Disclaimer, I love handwriting. TL;DR handwriting = write only + self-expression
I think that handwriting and its constraints, lead to a different mindset from when you're typing on a keyboard:
- It's write Only; You can't erase easily, so you either accept it and just keep pushing forward or you get distracted by not being able to do so (good), leading you to think twice before writing (bad).
- The physical coordination involved is a soothing and mindful process (at least for me) and it feels much more creative than typing. It's way easier to stay focused while doing so (might relate to my ADHD).
I rememeber vividly myself asking my dad when I was a kid why his handwriting was so different from what I learning at school. He told me that the success criteria for writing is can you read your own writing? Can you make an effort to make readable for others when you intend it to be read by someone else? If yes, that's good enough, nobody cares if you draw letters in a uncommon fashion, as long as they can understand the words.
While questionable at times, the way that doctors write follows this logic, because when writing the prescription the tend to optimize for writing more than reading, and therefore allow themselves more freedom.
I feel that once you've taken that step, writing becomes a much more enjoyable process. When I write, a "f" will be drawn differently, depending if it's the first letter of the word, or in the middle (as in "effort").
So I end up having three "modes" for handwriting:
- Ephemeral, I'll write things so quickly that I know I'll be able to decipher it only for a few days, while the topic is still fresh in my brain.
- Just for me, so I make zero efforts, just paying a bit more attention so I don't end up scribbling "effort" into "e||o||" which may cause problems in a month or two.
- For others, where I'll keep my handwriting peculiarities, but make sure it's absolutely decipherable (so no shortcuts, no stroked words, etc ..)
Strangely, I remember myself handwriting things, but I never remember typing something (though I'll remember about the thoughts of course). It's like handwriting is a more anchored experience somehow.
While I'm not sure I see as much games being review bombed for political reasons in my sources for video game reviews, I strongly agree with you that it's really hard nowadays to find high quality reviews. It's always been bad in mainstream video games medias though, but underdogs that are more open to criticise game tend to not last very long.
The best approach I've found is to become aware of who are writing the reviews I perceive as high quality and simply follow them when they change medias and pay attention to what they communicate about their current position.
Ultimately, the best reviews are almost always coming from sources that have a business model that doesn't rely on ads.
I'm wondering if that has to do with the time spent writing Clojure code?
I have only wrote LISP code during uni and on pet projects and I always feel like the parentheses are making things easier to visually process. The AST is explicit and basically just before my eyes, and it looks nice because of the functional style.
That's an ambitious goal, I'm not sure to see how that would be maintainable on the long run.
On a much smaller scale, if anyone is interested, I maintain a black list focused on those code snippet content farms that gets in the way when you're searching for some error message or particular function here https://github.com/jhchabran/code-search-blacklist.
To shed some lights on why power sliding is so unreliable, doing so requires to be familiar the surface on which you’re attempting it. Being familiar with it means that you basically failed to and fell down multiples times before getting it right, which already requires a good skill level.
And you cannot assume that power sliding on a surface will be similar to another one that looked the same because a slight change of humidity, dust or grease may totally change the outcome and transform the slide into a hang up that will throw you at the floor pretty hard.
So if you combine a really thin margin of error with the inability to confidently execute it on new surfaces, it makes powersliding a pretty unreliable way of braking unless it’s an emergency, in which case jumping off the board is much easier.
Meanwhile, you can power slide at will in the skate park because you know the surface by heart, and it’s easy to get it consistent by how many times you just rode it.
Regarding the weight, it’s a different position when you’re holding it at arms length while playing. You don’t hold your iPad in the air while reading, you put it against your knees or something else!
If anyone wants to give a try, it's worth noting a few things if you come from vim:
- if you are on osx, you'll may find the gui rendering quite laggy if you are using a Retina display. Using the terminal will make it snappy again. Using something like Alacritty will make it even snappier if you're sensitive to it.
- if you are on linux and use the gui, the pgtk branch is worth giving a try, it drops the old extremely outdated Xt code
I would say that what areally changes the game is to use evil (vi style bindings, 95% stays the same) with Emacs so you keep the muscle memory and you can keep making use of the common ex commands.
I have gone back and forth between vim and emacs, usually for a bunch of years each time before currently settling on emacs with Doom. With the nativecomp branch, it's actually pretty snappy and doom emacs is a great setup to get started without drowning in the amount of configuration.
I would say that I just love vim style input and modal editing, but doing that on top of emacs with evil mode and elisp is a better match for me than vimscript. The feedback loop you get with LISP and emacs is incredible when tweaking things to your liking.
Every function is accessible, there is just a global scope and you can call pretty much anything. It's sounds like an horrible idea, but it also means you can quickly hack stuff by reusing the internals of a package you like.
For example, it took me half an hour to initially POC this https://github.com/jhchabran/ivy-lsp-current-buffer-symbols by just skimming through the emacs-lsp codebase and randomly trying funcs in the repl to get an idea of what each function was doing.
May I advise to give a try to Doom instead? It has less ambitious objectives [1] and feels much snappier while providing a similar experience (vim-like, out of the box)
Also, if you enjoy the experience provided by emacs + evil, giving a try to the native compilation branch of emacs 28 gives noticeable improvement in terms of speed.
Heetch is a ridesharing company that handles 150k rides per week. We're providing young people with an affordable and safe way to enjoy their nights. We have raised is $20M in January.
Our engineering team is operating entirely remotely across Europe.
We're hiring an Elixir engineer, to join us in building a transverse team that is focused on improving the productivity of other developers in the company by spotting generic needs across teams and addressing them in the most impactful way.
This is done through various means such as introducing a new technology or designing a creative solution to a problem shared by multiple teams and shipping it as a library.
We do this through carefully collected feedbacks, analysis and is delivered iteratively, following closely open-source methodologies. The team also allocates an afternoon per week to work directly on open source projects and blogging.
We're running a Go/Elixir microservices (90+ atm) stack and our mobile clients are built in Swift and Kotlin. We're using a lot of Postgres, Redis and lately Kafka.
We provide great pay, a conference budget, a travel budget (wanna physically pair with someone for a specific project, go for it) and other perks.
Heetch is a nightlife ridesharing company that works with 5,000 professional drivers and handles 70,000 rides per week.
We're providing young people an affordable and safe way to enjoy their nights.
We just raised $12 Millions and we're looking for data, infrastructure, backend and mobile engineers.
Our engineering team is operating entirely remotely across Europe.
We're running Go, Elixir and Ruby microservices in a mesosphere dc/os cluster. We're using Postgres, Redis, Rabbitmq and we're moving toward Kafka and Spark.
Our mobiles apps are using ReactiveX, iOS app is mostly written in Swift and we've just started to use Kotlin on Android.
Valve just released a big gameplay update to its biggest esport game and added support for a bot scripting api along the way, allowing players to exchange them through Steam workshop.
> Programmers, scripters, and mad scientists rejoice! You can now create your own Dota bots using a brand new scripting API. Upload your bots to the Workshop for others to download and play. Then, enjoy watching as your creations slowly take over the Dota universe.
Basically, there's now an API to play the game through bots and make competitions between them. Given the deep gameplay the game has and the available API, this hints of a very promising bot programming scene.
Trainers, save editors, translations are basically a common entry point into programming, like a closed knit group of people that love video games and who wants to modify/hack/translate their favourites games. At some point, programming comes to the table and people will start sharing knowledge about it with their own way of doing things. A popular project will get hosted somewhere and the following projects will get hosted there too, simply because they're learning by looking at the popular one. Rapidshare, megauploads, all of these are tools people know before getting into programming, so they just use it. Github is something that comes later, if things get serious.
Dwarf fortress stuff is like that, Minecraft is even worse, you get adfly in the middle :D
As a Vim user, I consider the whole productivity thing about it quite over-rated. Yes it's efficient, yes it's faster, but in the end, anyone with a decent editor is going to go faster after a while.
The point is comfort. Once vim's mechanics are assimilated, you starts to memorize meaningful sequence of letters, like ci". And those sequences are just words you're typing, so typing code or entering commands is exactly the same thing.
And none of this require going too far frome the home row with your hands. This in my opinion is why Vim is so good :)
Well parsing the vimrc might be too much as it would require a full compatibility layer and I highly doubt it'll ever happen. Using vanilla lighttable config wouldn't bother me, even if I have to rewrite most of it. It's a different editor after all.
But yeah, all the "vim" layers around are basically just the bindings, in normal and insert mode which just half of vim. If we can't change buffers with :b, :A or anything, it's just painful as a vim user. Same goes for what you listed.
I have great respect for the guys at code mirror, it's just that I view it as just a quick hack to add vim bindings that a real vim like solution. If LightTable advertises about being vim friendly, there should be an implementation that keeps the vim workflow, not just small bindings.
As a vim user, I'll just skip the "vim" mode if it's done like that (and sadly I'll stick to Vim even if I really crave for a modern "vim" with a decent scripting language).
As I've just scratched Scala's surface, I don't get what you meant by the community status. Considering how important the ecosystem is, could you point some resource to understand ? Thanks
They do make money out of it, not that much but they do. Most of the time, it's so small that we don't have a clue on why they do it. For sure there must be some sort of gold diggers trail spawning vocations, but they wouldn't do it if it wasn't profitable in some way.
The key idea is where do you live: if I'm living in a poor country where average salaries can vary from $50 to $400 per month, imagine how much I can make by send viagra spam by just sending emails to doing hard physical job ? For us it's not worth even doing it as a hobby. For some people, it's damn profitable, just take the case of Nigerian scammer, convincing someone to send him $500. He's doing that every day, if he can scam one "wealthy" person to do it once per month, it's damn profitable. Yeah, this isn't really a shiny way to make profit, but you may understand the motivation behind it.