Comments URL: https://news.ycombinator.com/item?id=49138188

Points: 563

# Comments: 63

Crazy that despite their progress behind the scenes, they appear to have not touched this website since.

I probably spent a little too much time tweaking the CSS to get the mosquitoes to not overlap the text on various viewport sizes :)

HN discussion: https://news.ycombinator.com/item?id=43518462

Lazy research, lazy writing, disappointing but not surprising.

With Prism, you can then create tool suites like syntax_tree [2], which then leads Prettier formatters [3], a new Ruby LSP [4], which unlocks a new Ruby LSP VS Code extension [5], not to mention a laundry list of other gems like Rubocop and of course Ruby itself that will benefit from a faster and more maintainable Ruby parser.

It's a beautiful illustration of the power of questioning conventions, going back to first principles to uncover better solutions to previously solved problems, whose new solutions create new capabilities which unlocks the ability to solve new problems.

[1]: https://github.com/ruby/prism [2]: https://github.com/ruby-syntax-tree/syntax_tree [3]: https://github.com/prettier/plugin-ruby [4]: https://github.com/Shopify/ruby-lsp [5]: https://marketplace.visualstudio.com/items?itemName=Shopify....

Comments URL: https://news.ycombinator.com/item?id=37878108

Points: 2

# Comments: 0

Everyone knows the "ton of money" doesn't come from working a salaried job, it's from creating something new / starting a company.

But only US green card holders or US citizens can even dream of considering that as an option they can pursue.

Also I-485's i.e. Green Cards, Permanent Residence status, in the US are based on where you are BORN not which citizenship(s) you have.

But the solution can be all of these proposed "it's just this" strategies combined.

We do need a: - standardization of plastics, - a switch to alternative materials that are more compostable, - a research lab to more deeply understand the true nature of plastics and their reuse, - a tax on environmentally costly materials such as plastics, - depolymerizing, - and more...

These are all solutions to the same problem. Let's work on all of these problems simultaneously and combine them for compound effects.

Seems like an area of concern / gotchas. Either restrict Data to not allow mutable nested objects, or provide immutable versions of stdlib object types as well and enforce that those types are used.

Yet another Rubocop-that-should-just-be-built-into-the-language coming in 3...2...1...

The only reason as a dev you would really care about this is if you navigate / search code by scrolling until you find the function you care about. The invention of Ctrl+F makes this strategy of code navigation obsolete.

In my opinion ordering should be something along the lines of:

- initializer / constructors

- public functions from most commonly used to least common, with similar functions (perhaps with different inputs) being close to their relatives, and functions that call each other being close to each other

- deprecated public functions

- private functions following a similar ordering pattern to public ones, ordered by most used by the public functions to least used

E.g.

p: or f: instead of path: for filenames

l: instead of language:

-f: to exclude specific filenames (makes it easy to filter out tests)

You get the idea.