skysight-inc/HackerNews huggingface dataset:
Not the OP but my take is that Typescript has done great things for improving JS but it's still JS and carries a lot of it's baggage with it. There is only so far you can take it while maintaining compatibility and the type system is overly complicated in places because of this. It also doesn't really give you the same guarantees that something like Rust does, I don't believe the two type systems are that comparable. On top of that unless you use all TS packages types are maintained and installed separately adding to an already tricky to maintain dependency graph that comes with Node development.
> ARM has a more relaxed memory model that allows you to skip some uarch components.

Note that ARM still generally supports ldar to match Intel’s semantics.
We probably have similar views, with some differences.

We definitely have and will pick up inspiration from the brain as you point out.

That is especially true in terms of the basic topologies of our brains neural networks. I.e. the painfully simplified artificial neuron model, two layer networks (which may roughly corrrespind to some single biological neurons that can have hierarchies of dendrites as I understand), then deep networks, convolution, recurrence, competitive layers and other topologies.

But I think the freedom of math to produce global algorithms directly allows faster innovation in a way that incremental change via evolution never had.

I expect GAI will always have some biologically inspired roots, but my untested (obviously!) opinion is that the first GAI will significantly benefit from global gradient based algorithms, and incorporate symbolic and database sides too.

The latter two not looking anything like how our neurons operate.
What does he think will improve? Migration for the sake of migration is a waste of everyone’s time.
> Sweden hasn't even been worse than the 2000 Flu season yet.

Can you post the link to the Swedish statistics? I think you're counting flu and covid death differently.

For flu I think you're using a mix of all cause mortality and statistical modelling. For covid I think you're using either "died after being tested positive for covid" or "covid was mentioned as a cause on the death certificate".
Article seemed to miss one critical aspect of biological neural networks of emergent and self organizing behavior from individual cells and up (eg. local and global collective behavior is emergent).

I am most familiar with NEAT methods, in my perspective even NEAT most advanced algorithms do not come no where near in modeling self-organizing processes similar to biological networks.

I have no idea where author of article come up with ~110 neuron module, because one cubic millimeter of cerebral cortex contains roughly 50,000 neurons, each of which establishes approximately 6,000 synapses with neighboring cells.
That's funny. I see that happening with some words or names especially (I can't remember an example I realized the other day).

It might just be that the brain "shortcuts" some things and change the way it's perceived. Insertion of an r in some places is an actual linguistic phenomenon (more on the Otellini case).
What happens to all your connections if you stop owning Apple devices?

Sounds like a nice way to keep you locked into a very expensive ecosystem.
Gitlab is functional and has more features/functionalities than Github.

But,UI wise , Github is very much slim ,fast and quick. It will function without js. Gitlab although functional will take very much time to load a page(because ,js is used a lot).Making it PWA would solve the problem but it is still not made PWA.
I think as of today, if the server side of programming we are talking about is really web application, languages don't matter.

Pick one you are familiar with, the language the toolchain and the overall ecosystem, it should just work.
On the Consolidation of the Web
Didn’t they acquire Annapurna recently and are making their own thing?
Wow, what a read. I’m sure GitLab has improved and grown a lot since then, but that’s like a comprehensive list of what not to do from an IT perspective. Not ever checking to see if your backups are working, wiping production DBs without a second thought, this post has it all.
Many books that just give an overview of QM don't use dirac notation; look for books with "Modern Physics" or "Introduction" in their names. However, Dirac notation is used so ubiquitously in QM that your question is a bit like asking if there are linear algebra books that don't require you to learn matrix notation. Sure you can do linear algebra without matrices, but that would be a bit eccentric today.
Why wouldn't you just use OCaml, Haskell, F#, or Scala, where you've got much more mature web framework options? Don't get me wrong, Rust is fine, but if you don't need its memory management then why make trouble for yourself?
Show HN: WYL Today? A note-taking utility for tracking what you've learned
I just setup auto deployment of my Android app to the app store view gitlab-ci, very cool. At this point im not sure if I should spend the time to replicate this in github actions on the copy of the repo.
Slack or Google can be used as sign-in options, email can also be used once a team is created but not for the initial registration.

There is a community PR that's being worked on to make the auth system a bit more pluggable, I'd link if GitHub was online.
Benchmarks while emulating x86_64!
This is one of my favorite quotes. I personally take it to heart and interpret it to mean someone being an expert only earns them the right to be listened to. It’s the arguments that matter - they still need to make a good case if they want me to believe them.

Often though, scientists never make convincing arguments to the public - you need to find specialist forums and blogs where they argue amongst each other.

So it’s no wonder we have such an issue with the public’s lack of trust.
How do you run the server? Create a packer image? Init scripts (or something similar)? Keep track of whether it’s up or not?

For developers who have grown up with containers, kubernetes offers the simplest, most familiar way to deploy a service.

I recently had to setup a factorio server. The official guide mentions downloading the binary and using init scripts to get it running. I tried to debug obscure issues with the binary for a few hours before getting fed up and looking for a containerized image; once I found that, it was super easy to start one locally. GCP offers a “container on VM” feature which I then used to deploy the thing in minutes. The experience felt so easy.

Notice that I did not use kubernetes, just something that can run containers. But if I had more apps to run, most likely I would set up one.
The really sad thing is that the FTDI clones worked better than the original ones.

The original FT232R chips have a clocking bug that makes bitbang mode unusable for many applications, with no workaround (their errata sheet suggests a bullshit workaround of setting the clock speed to max, that is unusable in practice because USB can't keep up). It's supposedly fixed in a revision that I've never seen, and I believe they never manufactured it.

The clones... work perfectly fine: https://twitter.com/marcan42/status/695292366639378433

In fact, I reverse engineered FTDI's bricker, and it works by exploiting the fact that their own chips violate their own interface design by requiring EEPROM words to be written back to back - even word writes alone are staged and ignored without an odd word write. The clones honor the writes independently, like FTDI's other chips. Their bricker code only writes even EEPROM words and preimage attacks their own checksum algorithm (since the real checksum is at an odd word they can't touch) to make it work, so it has no effect on the real chips (which get sent the same commands). It's hilarious.

Don't buy FTDI. They're just bad.
> Bob Dylan befriended him, Joni Mitchell helped support him, and the Eagles covered one of his songs. So why did success elude the late singer-songwriter?
Rewriting is very expensive, and the advocate will need to make a VERY strong case for Rust if they're asking your company to invest in replacing it - and alternatives have to be suggested as well, including other languages and a good list of things wrong with Node / TS. Consider developer availability as well.

I don't think a strong enough argument can be made. I'm sure you CAN write web services in Rust, and that in very specific cases it'll have some benefits over Node, but honestly very few people work in an area like that.

Disclaimer: I've settled on using Go to rewrite an existing application. The original app was written in PHP; nothing wrong with PHP per se, but the existing codebase is a mess and the PHP version is hard to keep up to date because of LTS versions of operating systems + very slow and careful updates at our customers (it's network infrastructure). For me, switching to a compiled language that produces a self-contained executable was a compelling argument. I have to admit that I do kinda pine for something like Java again though.
V8, JVM, CLR and others are well proven runtimes providing a well functioning sandbox, but of course we test a lot. I am sure you know what the risks are with native code - you're a native code proponent after all; any code running in a medium and bigger company that could misplace money is a huge liability.

I don't know what magic you're talking about - we're simply waiting for WASM to standardize GC, SIMD, tail calls etc, you can read more here[0]; and to get the execution optimized like V8 did over the past 10 years[1] (WASM on V8 gets most of these gains by default as a bonus).

I already said why I want WASM: because it provides a good sandbox and opens most ecosystems through safe and typed interop. I don't care about ES modules in particular - I care about ES modules, Ruby modules, Python modules, Prolog modules, Fortran modules, C modules, Rust modules, AssemblyScript modules, COBOL modules, Erlang modules, F# modules, Java modules, and so on - at once. Finally a future where I can use and trust any library and not get limited to the language I use (if I don't want to spend most of my time fighting and securing C ABI interop, if at all humanly possible) is there.

[0] https://github.com/WebAssembly/proposals

[1] https://v8.dev/blog/10-years#performance-ups-and-downs
Once there is no cheap labor left we will see an incredible amount of consumer inflation because prices need to rise to accommodate higher wages.
Please don't do this! Say you have a cashing service on the same pod that temporary holds the resources most frequently needed to deliver some business value, why not just use a cashing library that does nothing more than protect a hashmap with a mutex lock and an eviction algorithm carefully tuned for the data access behaviour? Sorry but stuff like this just pisses me off, go play with Duplo if software engineering is to difficult for you.
Could you provide details on how you plan to be more reliable with a self-hosted solution? what kind of archtecture would you use? how many people will be involved in maintaining?
Jiu-Jitsu
Are his designs impractical to use?
correlation != causation though.
I would choose self-hosting for small to medium size teams any day. I can't fathom why people choose not to self-host at this scale. Your data. Your control. Your network. Your infrastructure. Your responsibility. Are people becoming more afraid of responsibility these days?
No, for example Microsoft will not produce a product in an unrelated market. Microsoft is unlikely to open a sandwich franchise no matter how much money can be made.
I've studied Judo and Bujinkan. If I did it again, I think I'd give Krav Maga a try. But then the grass is always greener on the other side, isn't it?

Anyway, just go find a dojo and show up. In any reputable dojo the first session is free, and like any trial it goes both ways. See if you like the teacher and the nature of the art.
I believe GitHub's been adding new features much faster after the Microsoft acquisition. Moving faster can lead to breaking things more frequently.
probably overly complicated layers-upon-layers of services, infrastructure and feature creep fighting with each other
Is there historical data of Github Uptime/Downtime? CSV format or other?

I'd love to do some analysis on how things were pre, vs post the acquisition (and trends in availability)
The BSL is meant to be open source "in spirit", with the sole restriction being that you can't run a competitive hosted service because that's the only way the project sustains itself.

Internally hosting a copy for your own company is purposefully within the bounds of the license.
I use Arch Linux, and have for over 10 years. I don't like systemd, but the documentation is really good and the AUR is pretty amazing. I've never really had any problems with it, and the performance is really good.

I've thought about switching to Void Linux (no systems), but I'm lazy and don't like trying new things as much as I used to when I was younger.

I chose Arch Linux a long time ago because I liked it had i686 binaries instead of i486 like Debian. I had a 32-bit CPU back then. Also it doesn't come with any crap, so that's nice.

I would like Arch to remove systemd.
> But I'm afraid there are 3rd party programs hardcoding it (and existing ARM hw they run on, etc.)

Of course just about every JIT runtime does this.
Probably both. I remember the very first versions of Gitlab when it was just announced on habr.com, and it used to be a minimalistic (more in terms of UI) version of Github. As the functionality grew, things got a bit out of control.

Currently UI looks more like it's been designed by people who write code rather than those who have spent considerable time thinking through user interactions and designing based on that. So it's not bloated in terms of the code and libraries, but rather all of the functionality is just thrown to the user as is without much thought.
The whole point of a business is to become a money machine.
Reading this I can't help but be lost trying to come up with any alternative solution for this specific use case that is worse than what they describe?

A bunch of mostly static blogs can be hand-edited HTML, or some ancient perl script, or any of the existing static site generators.

If it absolutely needs to involve server-side logic, it could be completely accomplished within a single call to ```rails init```, and the resulting project would incorporate a few $billion worth of collective experience commonly refered to as "best practice". It would be far easier to modify and far less likely to contain vulnerabilities. Performance would be worse by a factor of maybe x100, or "why are you asking these weird questions?" when converted to the real world, according to a representative survey of end users.

There's a good argument for replacing individual components on, say, the critical path for rendering people's twitter feed with lower-level implementations.

But it strikes me as unlikely that such endeavours would care about the ability of their ORM to quickly generate the migration scripts to drop or add some database columns.

So I can't quite see the benefit of cramming the rails model into Rust? Rails is spectacular in how it allows you to quickly iterate, adapt your data model, try some ideas, and so on. Those are qualities that just logically do not transfer to a world of static typing and manual memory management.
Einstein had the physics idea for general relativity first, and adopted the mathematics of differential geometry to try to implement it. People had the idea for quantum mechanics first, and then discovered that there already existed mathematics for it. For quantum field theory, there was no existing mathematics for it, so they invented their own. For gauge theories (such as the Standard Model), I'm not quite sure the initial motivation.

On the other hand, I think you could argue that Lagrangian and Hamiltonian mechanics were developed for aesthetic reasons, and these both proved influential for twentieth-century physics.
https://www.isitdownrightnow.com/github.com.html
Generally when I’ve successfully advocated for new languages or tools at work, it’s been by gradually introducing the language in newer and fairly self-contained projects where the risk is relatively low. This provides a safe space to explore all the concerns you just mentioned without compromising any working code.

If you have some interest in Rust, that’s what I’d personally recommend instead of migrating an existing service to a different language.
I did work somewhere once with GitLab self-hosted in a VM. The person in charge believed it was important to reboot the VM every so often.

One day, for whatever reason, he couldn't bring the VM back up. Self-hosted GitLab was out for the rest of the day. I found this pretty funny.
I'm a bit skeptical of sidecars. It seems like a pattern born of organization separation between ops and dev instead of an optimal solution.

I mean, I think I get the benefits. You have your magical smart pipes that just work deployed along with but separate from the grubby app code. Supposedly the app code is simplified because a lot of the complexity is handled in the side car. They're separate containers so you can "compose" and deploy them separately.

But in practice, why is this not strictly worse than a set of libraries? You're spending overhead and do you gain, really?

The side car is language agnostic...but you need a language specific library and you need to interface with the side car through some indirection (network, file, IPC) instead of in process execution. You DO consider the side car or you're double implementing the complexity in both the app and the side car anyway. Reaping the benefit is the same as depending on it, no? So now you have a dynamically linked dependency, so to speak.

Why not just save a lot of overhead and use a library when its viable and relegate the sidecar to a stopgap instead of promoting it as an optimal pattern?
I've been writing Python for a few years now (at my job), and most of the situations where I've used breakpoint() to debug something would literally not have been possible in Rust because they would have been compile time errors instead of runtime errors.
This really only works in the case that you have one server running a python app that you can ssh into. Any deployments more complicated than that and it starts to break down.
But again, in practice banks will loan more money more easily to those with a verified identity that has recourse beyond simple "loss of creditworthiness", so those loans will always be more appealing to those who can get them, and so nonrecourse loans never become a thing for normal citizens who can avoid them.

And those who can't get shunted down into the "Payday Loan" tier of finance and they have to dig themselves back out with the equivalent of deposit-backed credit cards.

But few people will choose a deposit-backed card when they have the option of trading identity for better pricing / convenience. If the online ad industry has taught us anything it is that mainstream consumers will trade their data for even the smallest of considerations.

Even if decentralized financial identity would be an improvement (and it is not clear that it would be), a vision with no practical incentive to get there from here is just the basis for another startup destined for whatever is the spiritual successor to f*ckedcompany.com.
> Would the symmetrical statement, that you can only meaningfully believe an expert if you are humble and have done your homework, be true?

Yes and no.

Yes, because as you point out, you need to be able to verify if you are to really trust someone.

No, because the society is largely built on trust anyway, and as long as you can trust other people to verify the claims then you don't need to verify everything yourself.

(That probably explains why so many libertarians have certain anti-scientific beliefs, if you don't have trust in the society at large, there is no way you can verify all the research.)

> I don't generally get the sense that "skeptics" of whatever color are less informed than the orthodox.

I get the sense of that a lot in the global warming debate. If the deniers understood the basics of the theory of global warming, for example, that it predicts (and we observe) stratospheric cooling and polar amplification, they could never claim that it could be the sun.

With vaccines I think it is similar. I don't know much but I would bet there are classical experiments and observations that establish how the immune system works, and these pretty much lead you to the current theory.

Which brings us to a point - if someone argues too much against a scientific theory, but are unable to create a decent competing alternative, it is probably a sign they either haven't done their homework, or they don't understand that scientific theories are supposed to be only the best available explanations, not anything more.
> We have customs enforcement to stop goods at the border and a court system to deal with internal disputes

It's a joke, right? This system has allowed everything from fake hats to fake, well, everything, to come into the country undeterred. Amazon and eBay are full of the stuff. It's so brazen that they are not shipping fakes directly into the US through highly subsidized door-to-door shipping using the US Postal Service.

And you want them to police an obscure little chip out of millions that come through the gates? My friend, our system is powerless against the onslaught...and they know it. Sure, a few things get nabbed here and there. This is a rounding error at the scale and breath of what's going on.
At work, we have an employer-provided (some groups also have their own server/setup) GitLab instance. I work on there much more than on GitHub, and am really liking it. Everything seems neatly integrated, especially the CI/CD is nice.

For all I care, GitLab can remain as it is right now. My primary fear is for it to become too bloated, trying to be all things to all people (project management, CI/CD pipeline, bugtracker, Wiki, Git repository, ...).

I would be happy to find out about people's experiences rolling their own GitLab, like what pitfalls to look out for. We are on GitLab CE 13.1.3. The biggest bug plaguing us has been CI/CD failures [0] for no apparent reason; but this is solved by a

retry:
max: 1
when: runner_system_failure

block in the CI YAML, and seems to have been fixed for new releases.

[0]: https://gitlab.com/gitlab-org/gitlab-runner/-/issues/4450
Pinebook Pro – The first impression of a $200 ARM-based laptop
What is your opinion on Filipino martial arts ?