Hacker Newsnew | past | comments | ask | show | jobs | submit | more self_awareness's commentslogin

Why would a new rewrite be better preservation strategy than a full refactor and refresh of existing stable and working codebase?


Why a new incomplete implementation would be better to use than a project that is stable, full-featured, and with a proven track record?


You seem to be new here, so you probably don't know that:

- Even if you separate each point with a new line, - HN formatter will join everything to one line anyway. - So it's not OP's fault his points are in the same line, because the source post has them in separate lines.


Join

date

of

an

account

means

nothing,

bro.

Gold

star

for

the

decade

of

participation

though!


Some other guy tried it as well after you, also no luck.

One strategy is to wait for US to wake up, then post, during their morning.

Other strategy is to post the same thing periodically until there is response.


I don't know if you're harsh, but one thing I've thought before I've clicked the link was "oh, another gui toolkit reinvention, I wonder how many times it will reinvent what's already invented and how many already solved problems it will simply ignore".

Well, I guess accessibility is one thing it skipped. It's a huge topic, I admit, so I'm not particularily surprised, but I think a better way for the author of this series would be to promote already existing huge toolkits that do have lots of functionalities built-in, including accessibility, like Qt for example.

That would be good also because already established huge toolkits have already answered a lot of important questions, questions which "modern" GUI toolkits simply ignore. New generations won't even know what we had when we were young.


The point of this isn’t to make another production-ready UI library. The point of it is to learn how UI libraries work by doing it yourself.

Do you walk into a beginner woodworkers class and scoff at them for making yet another birdhouse?


> oh, another gui toolkit reinvention

Imagine wanting to understand how an existing technology works…


It looks like WinAPI Window Management via CreateWindow / SetWindowText / SendMessage.

https://gist.github.com/a3f/22d0d2688b56e79865f8



Did I ever tell you you're my hero?


Home pages: Ruby 4.3mb, Python 1.3mb, java.com 2.1mb, raku.org 360kb, typescript 2.1mb


Yeah but them's highway miles. I have much less care about a site loading images than the stuff that makes the mobile nav work. Images are pretty!

For instance, here's Python's 144kB JS-powered homepage mid-load: https://imgur.com/a/OvYVAMS

And theirs doesn't even have any pretty images! That said, Ruby really ought to give those images a compress.


I really wanted to like Ruby, but the ecosystem is just... broken.

Comparing to Python, where virtualenv is de facto default, and pyls works by default, the experience with Ruby is not that great.

New website looks like a website for a startup project that will be closed in 2 years.


What is broken in your mind? What things did you have a "not that great" experience with? There are de facto standards and defaults in Ruby as well.


Well, for starters, I never got LSP to properly work with Ruby at the same level as other languages, i.e. so it's possible to browse the standard library.


Which LSP are you using? I'm using both solargraph and ruby-lsp and both works fine by me (in neovim).

Although those who really care about LSP support usually will use RubyMine IDE instead. Some of my colleagues are going that route, and they're mostly coming from Java (or similar background)


I'm not really "using it", I'm just trying every now and then, and I keep encountering errors, hangups, and lack of functionality. Now I've tried ruby-lsp, and it just sits there on "Starting Ruby LSP...\n"

Couldn't even install Solargraph, once it errors out with 'Kernel#require': cannot load such file -- yard, other time it installs, but "solargraph scan" fails in runtime with "missing gem date" error.

Sorbet doesn't even work in VSCode, some bugs are over 5 years old.

But yeah, downvote my original post, because apparently all of the above is obviously my fault.

RubyMine was paid until recently, now it's free only for non-commercial use. It's also not really suitable for small scripting.

Historically, one insanely huge advantage of Ruby was that it was pre-installed on macOS'es, but I think they've stopped doing that since some macOS version.


> I also paid for a pro version of the OS.

Yep. And you got what you've paid for.

Look at it. This is "pro" now.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: