133 karma · joined August 16, 2007
The debate thing was just the impression I came away with. Things like this post[0] from late 2018 saying
> We are currently 32-bit only, and need to decide the best path for adding 64-bit support, should we elect to do so.
(and some other back-and-forth I can’t find at the moment) left me thinking it was an open question. I’m glad to hear it’s on the roadmap.
Anyone know how likely this is to change [soon]?
Even if neovim goes belly-up (unlikely), or totally diverges (slightly less unlikely), they’ve done a huge service to the vim community simply by existing and offering compelling, thoughtful enhancements while respecting the core spirit of vim - and being exceptionally mindful of practicality in how they approach changes.
Probably one of the best-ever examples of a fork that is Doing It Right.
For non-vimmers, a good analogy is the shell: would you want to replace sh with a more robust language like lua? Few people seem to enjoy writing larger programs in sh, and are quick to jump to perl/python/ruby once a script crosses some complexity threshold. However, I doubt many people would want to give up sh for interactive use. Mainly[0] due to omitting “cruft” like parens/quotes/commas, and also pipe syntax. Minimal example:
ls -laht | grep foo
is nicer than grep(ls(‘laht’), ‘foo’)
especially when you’re doing thousands of commands of varying complexity every day.Vimscript is similar, again mainly due to omitting “cruft” like parens/quotes/commas, and also some specific sugar. Minimal examples:
iabbr cosnt const
is nicer than iabbr(‘cosnt’, ‘const’)
and s/foo/bar/g
is nicer than sub(‘foo’, ‘bar’, ‘g’)
especially when you’re doing hundreds (thousands?) of commands of varying complexity every day.Besides setting options, the vast majority of the “meat” of my config file boils down to these types of commands, and is thus much more readable with the cruft omitted, even though I only have to type it once.
This could probably be addressed with some light syntax sugar on top of lua, and I think I remember seeing some comments from the Neovim folks about this very thing, but I’m not able to find anything concrete at the moment. Does anyone know where this stands?
—
[0] Of course, another issue (for both shell-scripting and vim) is the huge amount of tools built on top of the existing language, which we may be remiss to abandon. For shells, it’s probably practically impossible. For vim, I suspect it is possible, though it would be painful enough to merit a long hard think.
They and their patrons (myself included) would likely be very interested in anything/everything you're willing to upload.
Getting it in a reasonable form factor and some practical issues (stinking up the house) seem like roadblocks, but I wouldn't be surprised to see something like this come back around, focused on gaming.
Looking for someone with a deep knowledge of ClojureScript - and the browser environment in general - who can help build and evolve (and open source) our internal reagent-powered UI toolkit. Should be able to blur the line between frontend/backend development - care about getting small UI details right and not be afraid of diving into to server-side Clojure when the need arises. Bonus points for experience w/ a variety of past/present UI toolsets & techniques.
We're a small, smart team/company run by developers & we care a _lot_ about UI development. You'll be hard-pressed to find a team more dedicated to making a great product, or an environment more amicable to this kind of work.
Email me (ceo, product/ui lead) directly: jr@rafflecopter.com
Looking for a CSS/HTML master to help build UI's & own the "front-front end" of our application stack.
At the end of the day HTML/CSS are just tools. What you really do is breathe life into interfaces that millions of people use every day. You get the details right. You make computing enjoyable, an experience which is too often the opposite.
We have a ton of interesting work to do and you'll be hard-pressed to find a team that cares more about making great products, or an environment more amicable to this kind of work. Come focus on perfecting your craft in a place where the CEO cares as much about it as you do.
We don't really care where you went to school, job title buzzwords, or any of that. This is a position where a portfolio speaks louder than any credentials. We want to see your work!
(Note: this is _not_ a design position. We're evaluating the quality of the implementation, though of course it's impossible to entirely separate the two - like writing/acting).
We'd also like to hear more about the projects you've worked on, what your role was, what went right/wrong, etc... We're looking for real experience.
Remote is absolutely OK, though we do have some bias towards local candidates. (Boulder/Denver area)
To apply, email jobs@rafflecopter.com or me personally at jr@rafflecopter.com
(edit: beat to it!)
Thanks!
That and they give out awesome t-shirts :D
But, aside from the "masochistic" part of it, the community is unbelievable and the atmosphere at races is what got me into them to begin with. It's like one big family in a way. One big family that gathers at the most beautiful places in the country before sunrise so the
Thanks for putting in the time to help others. Keep up the good work.
Thanks. And I guess we're out of luck on an open-source Backboard clone...
I think the reason for the recent high-profile assault is not zeal on the part of the people actively decrying IE6. They just realize that sometimes, to make change happen (especially change this “drastic”) is to make a lot of noise. The squeaky wheel gets the grease.
They want people to stop using it, instead of just refusing to design for it for 2 reasons (and maybe more):
1. As web designers/developers, we are passionate about people having a beautiful and pleasant web experience. If we just stop developing for IE6, everyone who hasn’t dropped it may have a lesser experience, which just wouldn’t do.
2. Many of them may be forced to support IE6 by their respective powers-that-be, so the only way they can stop actively supporting (designing for) it is by getting a significant amount of people to stop using it.
I agree with you in general. I am never a fan of over-zealousness and pushiness, but sometimes that’s the only way to get things done.
But it's worth it. I'm getting pretty good, so who cares about doing actual work. :D
"do what makes you truly happy for the longest amount of time".
That implies some thinking about the future instead of blindly following something that may lead to short-term but not long-term happiness. Also, it requires that you figure out what makes you truly happy, not just surface-level happy.
It's a lot more difficult to accomplish, but so very much more rewarding.
:D
I appreciate all the help!