asdkhadsj

From an ex Go-er (5 or 6 years professionally?), now in Rust for a bit over a year, I can say that Rust in the majority of the cases is "just as easy" as Go.

The thing with Rust is it gives you a lot more of the complexity rope if you desire to hang yourself with it. But, a realization I had early on, was that I didn't _have_ to. Not everything has to reuse perfect lifetimes or maximum possible generics. You don't have to chase every latest feature (Async, I'm looking at you). Without all of that, Rust is still an amazing language.

What I found most amazing after leaving Go was not something I expected: Iterators. Being able to easily mutate complex data structures, filtering in complex ways, zipping, chaining, etc. I could do the same exact thing in Go mind you, but in Go I found myself writing helper functions all over the place. In Go, my code felt so spread out, and was hard to just look at in one screen to understand. Rust (and Iterators) made so logic concise that you could view it in one screen and make sense of it.

Keeping code "locality" was oddly, by a large margin, my favorite thing about Rust.

It's not, imo.

It's an example of extremely differing philosophies - of which Rust is a great example of the opposite spectrum of Go.

I imagine there may be a couple other examples, maybe something like Haskell (I wouldn't know), but I'm guessing the author just knew Rust better for this comparison.

It's easier to illustrate problems that shouldn't be problems (in your eyes) if you have solutions for them - especially solutions that you believe work well. Rust's take on these nitpicks is something that the author clearly thinks Go is lacking on.

In my view, this post is a critique on Go and the "simplicity" mantra it has; and only that.

I would think because IPNS is IPFS.. and you asked how IPNS compares to BitTorrent. Maybe I misunderstand your question, but the reply seems totally on topic and a valid answer to your question.

Does this support WASM? I'd expect not given it's so small, but worth asking.

Weird, failed for me too - I refreshed and then it worked. Wonder why

I wonder if "synthetic data" could be used to proof ML? Ie, rather than start from a huge data set that you _think_ is clean enough to know what a Car is (or w/e), you could use a data set that is perfectly clean and the ML set could be tweaked to give the expected result.

Of course, that would still be hairy as you'd have to ensure your ML still performed on real data sets. All the clean data would do is allow you to write unit tests of sorts for your ML with more confidence than the all-too-common unclean real data.

No idea, just making stuff up. Interesting thought.

Wouldn't you be the one choosing the IRC server? I thought the point of this was if you wanted to run your own IRC bouncer with a web client, similar to a self hosted IRCCloud.

Not loading for me, just fyi. Too much HN traffic?

Commit count can vary a lot, perhaps? I know I commit far more than my coworkers, but that does not reflect the LOC or "amount" of work. I just visualize and chunk things up into commits more frequently.

Hell, I struggle with even normal restaurants. I like going out, my wife and I can afford it, but I feel like I'm going out for the freshly, crispy yummy food.. and yet, I always end up taking half of it home because they hand me a massive plate.

I'm thinking next time we go out we'll try and get the same thing and split a plate. .. and then tip as if we ordered 2 plates because I feel guilty to the server. Hah.

In addition to everything you said, there is also optimization issues of your goals. Eg, I like to think of myself as a very long term focused person (over the last 10 years, at least), but my ambitions outweigh my energy. So I have to balance in short term "play" as a way to destress and enable long term progress.

The fact that we're not robots in that sense makes this even more complicated as we can't just choose our long/short goals and stick to them, we often have to set them up within the context of what we can actually achieve.. which I think is often less than people think.

You'd be surprised. I have a Botvac and that thing can easily damage plenty of things in my house.

On that note, I love my Botvac. My biggest complaint though is that it has to "learn" a room first, without any sort of helping functionality. This is a problem in my eyes because the Botvac comes with an awesome in-app barrier system where you can tell it to avoid areas, but to tell it to avoid areas it has to have done a normal scan of that area.

It's a chicken-egg scenario. I can't keep the botvac out of my fragile areas without first letting it in my fragile areas.

Once scanned though, the Botvac's "no go" lines are awesome, and very accurate in my experience.

Yea, which is why I want a real frontend, not an emulator or w/e. Ie, there are real frontends for both Neovim and Kakoune. They let the editor do the real lifting, and they merely change the UI.

That is what I want, but in a super well presented manner. I'd happily pay ~200/y for that. BUT, I think this frontend would also have to have a "normal" editor built in, because I don't think people like me would pay enough to allow a dev to write this editor full time.

I think you missed Ps point completely. It was that if the ratios are off, the lower side has more of a supply.

What specifically each individual is looking for doesn't matter. It's supply and demand.

I like the CLI too, and would still need it if I "left" the Terminal.

What I mean by out of the terminal is that I simply want my editing experience to have variable fonts, popups, borders for windows that aren't bound to font size, better icons, underlines, etc etc.

God I hope to see some great looking editor like this (or Panic Nova?) with .. somehow.. integration with Neovim, Kakoune and etc. Aka an editor that can be a frontend to "classical" CLI editors.

I would pay so much to be out of the Terminal, but I need to use my normal editor (Kakoune in my case). I want to pay for a high quality frontend.

I fear the market isn't there and so the product I want will never be made. My hope however is that someday someone can make a great editor GUI that could be pluggable for users like me.

Simply a meme about exploiting your user data as extremely as Google can. Ie, I am their sole business model on the advertising front.

A good example is many of the things outlined in this post. People _trying_ to use Android privately, but after an update Google switches all of their privacy settings back to giving Google everything - and it syncs all old stuff to boot.

That behavior is what I consider actively combatant towards the consumer. It's like how Comcast just keeps finding ways to make incremental fees, "accidentally" charge people, etc.

These are under what I consider "evil" for corporations.

Depends on what criteria you care about. In the example of polling, and the data that can leak from said polling, it's only different in the sense that we _know_ Google is evil in this equation.

So if this is a concern of yours you should definitely not use Google, and you should probably not use Apple.

I was actually just thinking about implementing this type of importance based flags.

In addition to these, I'd like review stubs. Something like:

- REVIEW: can this be done better?

I'd like junior devs to be able to note things as they're thinking about it, not try and remember it later during review. Especially since there may be nothing wrong with the code, it may be as good as it can get[1], so a reviewer wouldn't catch it. Though, I'm mildly concerned about cluttering up code. I suppose you could just remove them on the fly down the line, since they made it past review and etc.

[1]: As good as it can get.. that the reviewer knows of heh

Nah, I just brought up Health as a general topic - one that has a deep pool of knowledge, more than a typical person even remotely knows, and also one that the experts in it's subfields advise against all sorts of things. What to eat, how much to drink, how much to exercise. My step mother didn't even know what a carb was, which I thought was basic understanding on food intake. So I used health as an example of a field where:

1. there is a lot of knowledge

2. the ramifications of not knowing things in that field are fairly high.

3. is a common source of experts advising the public do things differently. Eat less, exercise more, etc.

Which I think is somewhat the case here with Privacy and Information Tech. It's a problem that affects the public to some degree of severity, but "they" seem largely unaware of it.

It's not even a free problem, it's general pricing. Companies constantly seek ways to increase profits, while customers constantly seek bargain basement pricing.Electronic privacy is not a problem people have dealt with at large, I think. People also often view the competency of corporations much higher than the HN crowd typically does.

I think this is the same for any category of information though. Informed people will heavily advise against things that the public just has no idea on. Health is a big one.

My question is what can we do aside from running around in panic? It feels hopeless.

It is - I guess I just mean, the reply I was specifically replying to seemed to be concerned on if OP cared about the forking of React.

Vagueness and confusion all around, haha.

> Do you think that only forks of projects can have security issues?

Huh? I'm replying to someone inquiring why someone else didn't review a fork. Aka, the GP was focused on the Fork aspect of Hippy, and the Parent asked about React, as if React was a fork.

I think you misunderstood the comment chain. I was not even talking about security issues or how that affects forking. I was merely replying to another discussion about forking, and how React is viewed in that "forking light".

I think the issue is each module tends to include far more code than just what the project needed.

If everything was like the NPM meme where you install a package to check if something is true, then your LOC for that module with be quite limited.

However a single dependency is often big itself, and the 50 dependencies it has are also quite big. The LOC in the dep-dep is not the same as if it was written by hand in the dep.

So if you wrote your dep by hand you may use, say, 500,000 LOC - but with the tree of dependencies not being a 1:1 to what you use, you have to audit more like 2Mil LOC. Perhaps an audit could be aided by some sort of tree-shaking scenario, where all non-used code is removed, leaving you with the real 500,000 LOC that needs review.. Would be interesting.

I've been having this same problem with Rust lately. Frankly, I think it's true for any package platform you use.

Do you think that React Native was also a fork of something else?

> Why is that a good thing?

It (the US version) is not a good thing, correct.

What does a codebase look like with these API versioning exactly?

I feel like code bloat would be hard to maintain. Obviously I could take two endpoint handlers that have the same functionality and move their behavior into a shared function, but there's also tests to consider. As time went on, I'd have a pile of tests running against seemingly random versions.

Eg, `test_blog_create()` might test v1 and v2 of the API as that specific endpoint didn't change, but suddenly in v3 the API _does_ change, so now I need to write a slightly different test to handle that new functionality. `test_blog_create_v3()` or w/e.

I'm not arguing against it, merely noting what I've previously thought about as problematic for implementing versioned APIs.

Thoughts on how best to manage the code base?

I'm not familiar with this family of technology, so forgive the dumb question:

But.. what is this?

I read the landing page and browsed a couple examples and I have no clue what I would use it for.

Would it be a pile of distributed workers handling jobs? Sort of like pushing a job into a job queue and having a bunch of workers consume jobs?

If that's the case, what are some reasons I might choose this Bastion model over a more traditional JobQueue <-> Worker model?

Thanks to any replies. I feel I should be interested, but I'm confused :)

While I really love the colors and instructive nature of this product, I really dislike the dark oriented color sections. That is to say, I dislike how in a dark mode, it still has large sections of white backgrounds.

If I'm in a dark room, using dark mode and expecting lower light levels, a sudden white backdrop is blinding.

Perhaps these dark themes are intended purely for design, not how best to design a dark mode.. but I'd really appreciate more design around the dark mode.

Honestly, large color changes bother me quite a bit in our software these days. I remember I always hated Slack's light mode because it was a right pane full of white - very bright, and the left pane was a dark mode contact/channel list, very dark. Why? It has always been very distracting to me, and I don't get why people think dark and light modes are so easily mixed.

Perhaps I'm an odd egg. I dunno. I definitely know nothing about style. All I know is I view the brightness of applications to be the foundation and competing brightness bothers me greatly.

Also I already slept on it once, I'm not sure twice, thrice or hundreds of times would matter after once to me.

If it grossed me out I'd rather not sleep on it at all.