cy_hauser

A much better link. The underlying article there explains why they are being fined.

Because the incentive is now there. Maybe they don't get enough paid customers and want more money. This puts a bit of pressure to move a new feature that is really handy into the paid level. Then another and another. Might not happen but it could.

Most people using Datastar will not necessarily be smart enough to fork it and add their own changes. And when Datastar makes a new release of the base/free code people will want to keep up to date. That means individuals have to figure out how to integrate their already done changes into the new code and keep that going. It's not a matter of if something breaks your custom code but when.

Finally, many people internalize time as money with projects like this. They're spending many hours learning to use the framework. They don't want to have the effort made useless when something (ex: costs or features) changes outside of their control. Their time learning to use the code is what they "paid" for the software. Doesn't matter if it's rational to you if it is to them.

It looks like fennel and janet are from the same dev.

Interestingly, this didn't work for Jetbrains. They found people often skipped a year and decided they wanted the "missing" revenue. There answer is to sell the version you "own" as of the date they process your order. You're allowed a full year of updates. However, if you don't continue the subscription then your version automatically rolls back to the version as of your purchase. You lose all the fixes and updates you've been using during the year.

Too much overhead figuring out the good products ...

How does changing stores help. If the products are still the same but on Walmart, how are you getting better information?

How about Lit? I'm just looking at frameworks, components, etc. I was thinking of Lit as simplified web components? Is that valid?

Try Hack. I've tried many including Jetbrains Mono and Fira Code. Both are really good but I drifted back to Hack. It just hits a comfortable place for me.

I think it was the Go Marketing Team who decided to call it a boring language. "Boring" tested well for hyping the language.

True for the early days of Go but I don't know about now. I think the switch started happening right after modules came out. Generics and the new range stuff seem more for the sake of growing the language than specific needs in Google.

I did this about 1-1/2 years ago and just reran the numbers.

Today:

  "written|built in Rust"           1113 (1036|77)
  "written|built in Go/Golang"      1050 (889|25) / (119|17)
  "written|built in Python":         452 (422|30)
  "written|built in Javascript/JS"   286 (233|14) / (34|5)
  "written|built in Java"            115 (109|6)
  "written|built in TypeScript"       97 (89|8)
  "written|built in C#"               46 (43|3)
  "written|built in Stone"            13 (13|0)

  "written|built in Go/Golang"      918 (792|17) / (102|7)
  "written|built in Rust"           832 (790|42)
  "written|built in Python":        390 (364|26)
  "written|built in Javascript/JS"  269 (220|14) / (32|3)
  "written|built in Java"           107 (101|6)
  "written|built in TypeScript"      66 (61|5)
  "written|built in C#"              41 (38|3)
  "written|built in Stone"           10 (10|0)

Holy crap no. Take a look at the amount of sodium in Better than Bouillon. Way more than any other type of stock like product. You can get the rip-off box stock with no sodium added in all three flavors.

Oh, hi. Didn't see you there. Welcome to the web.

Nobody but you is suggesting we protect the rights of pedophiles. This argument is going where it always goes ... as the author pointed out. There are bad people in the world. They make up a small percentage of the population. You don't change society as a whole based on the behavior of these bad people. You do what is reasonable and within your ability. Did you even read article? By your logic would you allow the Catholic church to exist? They were literally protecting pedophiles for years.

To spin the wheels. People still get paid and the economy keeps humming along. No profit doesn't mean people aren't making money, just that the company isn't making excess money.

because their whole 2000’s-era style of online retail is past it’s peak and is starting to crumble beneath its titans

So what is the modern style of online retail that is/has taken its place?

I've ended up using at least a half dozen generic helpers in every application I've written since they were added. They've made my coding easier, more concise, and help with testing. Adding generics to Go was well-founded.

I think the pace has been extremely slow. So many of the changes to Go have been tool chain or library enhancements. Outside of generics related stuff, what are some added core language features that you'd prefer were not?

> "there's only one way to do it"

What's the one way to do iterators now? I thought this proposal came about because there wasn't a default way and everybody had to roll their own.

Replying to my own post for posterity because edits are closed and I missed the obvious Go/Golang. This pushes Go to the top winning it a "major award".

  "written|built in Go/Golang"      918 (792|17) / (102|7)
  "written|built in Rust"           832 (790|42)
  "written|built in Python":        390 (364|26)
  "written|built in Javascript/JS"  269 (220|14) / (32|3)
  "written|built in Java"           107 (101|6)
  "written|built in TypeScript"      66 (61|5)
  "written|built in C#"              41 (38|3)
  "written|built in Stone"           10 (10|0)

Yup, a lot of false positives without quotes. Searching with quotes on Story gives the following. (Search is case insensitive.)

  "written|built in Rust"           832 (790|42)
  "written|built in Go"             809 (792|17)
  "written|built in Python":        390 (364|26)
  "written|built in Javascript/JS"  269 (220|14) / (32|3)
  "written|built in Java"           107 (101|6)
  "written|built in TypeScript"      66 (61|5)
  "written|built in C#"              41 (38|3)
  "written|built in Stone"           10 (10|0)

Go is more like an climate that pretends to be an atmosphere for simplicity. Compared to a greenhouse you really can. Compared to the other climates it's essentially sophistry.

arguably... then I'll argue the opposite (even as a subscriber). Jetbrains rolls your subscription back to the version on the day you purchased, not the last version in your subscription. If you purchase and immediately find a bug, you know you're rolling back to that bug unless you pay a renewal next year. Same goes for any fixes you got during that entire year. Poof, gone.

I'm not understanding this. Wouldn't the lower bound on performance be the single thread? Any worse performance and you queue the write requests to match the single thread performance.

Go error handling is a bit rough. It's not hard to write the errors but they can derail my mind when I'm reading Go code. They're like walking up stairs where every fourth or fifth step is slightly higher or lower than the rest. If I want to take my mind off of them -- nope! I'm forced by their unrelenting placement to think about them again. Lots of Gophers get used to them though so it's a very subjective thing.

Some other (well known) quirks are:

-- Forced code formatting for everything. If you don't like it you'll probably never like it. It's mostly a problem if you're switching languages often.

-- Lots of little things you'll stumble on that have to be internalized. Loop parameter scope, variable shadowing, randomization of map iteration, the way slices spring to life but maps don't, colon-equals with multiple variables, no unused variables, etc. There are lots of "Go Gotcha" lists around and I believe there's even a book about them. Every language has them but they're especially noticeable in Go because (1) the rest of the language is so easy to pick up that they tend to stick out and (2) they can't be fixed because Go has a backwards compatibility guarantee that no breaking language changed will be introduced.

Anyway, I really enjoy Go. None of this is enough (IMO) to prevent anyone from at least giving it a try and seeing how it suits them.

Google's Go language is well suited for back-end code. However, it's a very opinionated and quirky language. If its style suits you it's a great choice. If, after looking at it for a bit, it doesn't sit well then nope.

Good idea but I can't seem to find a built in way to do this. Everything I've found involves third party apps which have all the usual problems that make me not want to use them: permission, ads, in-app purchases, battery drain, etc. Do you know of any way to do this that's already built into Android?

Says the thromrod!

users are more likely to use it since it requires very little effort on their part.

I use my tablet and laptop way more than my phone. I hate having to walk to another room to pickup my phone from its charger just to get one of these SMS codes. When I'm doing phone support I often hear, "hold on, I have to get my phone" when this step is required.

This looks interesting for businesses but at $1,000 per year and up it's a bit too expensive for casual projects.

For my house the problem is that the sun's energy is converted to radient heat which makes its way hours after the air has cooled. The HVAC people have said no amount of insulation or attic fans will help. They suggest radiant barrier roofing of varoius types. The simplest being reflective paint, which the HOA won't allow.