I'd love to see some kind of pre-populated sample account to play around in. My willingness to test out an app has an inverse relationship to the number of forms that app asks me to complete to view its functionality. In this case, i felt like there were quite a few forms that I needed to fill out to get to the charts.
Beyond that feedback, I think this looks really interesting and would love to see where it goes.
Did you read the rest of the comment? Without the link for context and given recent censorship of this kind of stuff I figured it might have seemed a little bit paranoid.
I'm a bit careful with monetization since it could harm the trustworthiness and independence of the platform, but once it gets more popular, I will definitely think about it. I could imagine a Buy For Life badge/widget that companies could integrate on their website.
I've implemented a few small toy languages before and Tabloid was intentionally sort of sketched out to be similar (expression-based grammars, whitespace-insensitive, recursive, etc.) so it was just mostly a matter of reimplementing those things with slight variations (the biggest being that entire phrases could be keywords). Doing so in JS made prototyping pretty fast.
I guess besides the fun of just the comedy of the idea I wanted to get back into JS (I haven't written JS in a while) and wanted a project I could fit into one night, so I sort of swizzled the language design so it wasn't super complex and doable in a few hours.
I think the points about people voluntarily building their businesses on Google's platform, and being thus beholden to Google's whims are well-made. The law, as it exists, doesn't seem to prevent that kind of thing since they're all private businesses, and this behavior benefits the consumer (arguably) even if it does hurt other businesses. Antitrust law (in the US) seems ill-prepared for the 21st century.
I tend to get interested in the policy concerns. Is web search so important that it should be considered a public utility, and thus regulated by the government? I think there's a case to be made there.
Having run a platform on RoR that did billions of requests per day, it scales just fine. It’s not as cost effective as Go, Java, Rust, etc., but it’s perfectly scaleable.
Scaling web apps horizontally invariably becomes more about where your data lives, how it gets scaled out, how it’s accessed, how work get processed (jobs), what caching you do, what memory requirements you have.... yada yada. Rails wasn’t ideal, but rarely are you ever working in a pristine “ideal” tech stack once you’ve hit scale and you’re 5 years into a business.
I think both statements depend on the definition of "at scale". I am no expert, but every RoR thing I have ever seen has been tiny in terms of traffic and still performed terribly. Is there anything in the top 100 sites using RoR?
I do think though there is a certain size companies like this reach where they go from innovative to being afraid to change anything lest the viral popularity goes away.
There's quite a distance between "tiny" and "top 100 sites"! Some pretty darn popular sites that use Rails (afaik) are GitHub, Shopify, Hulu, Twitch, and Airbnb.
Not really. The web has become massively centralized with almost all traffic going to a small number of sites. The bottom of the top 100 list is only getting about 50 million pageviews a month, even poorly written sites in slow languages can easily do that on very cheap low end hardware. Pretty much anything not in the top 100 is dealing with a tiny amount of traffic, even a fair bit of the top 100 is. So it is github and twitch, neither of which actually do anything substantial in RoR any more. That seems like a pretty good reason to think RoR's strength isn't high traffic volumes.
This is wrong. GitHub is still a large Rails app. See presentations by the core Rails team people who work there like Eileen Uchitelle and Aaron Patterson.
That's what I am going on. It literally says the RoR stuff is just the basic webpages, everything else has been re-written or was never RoR. Same deal as twitch, the RoR is just the trivial web portion which is mostly cached. All the chat and video is in go.
This may be true of Twitch but not GitHub. GitHub uses https://github.com/libgit2/rugged to bridge between Ruby and Git. As far as I'm aware, they still use Ruby to pull the diffs etc out of Git etc.
