HNHacker News
TopNewBestAskShowJobs

majidazimi

700 karma · joined August 7, 2013

submissionscomments
majidazimi··on New Research on How Ride-Hailing Impacts Travel Behavior
I'm a foreign student in Germany, living in a small city with 200K population. Public transportation is just fascinating compared to size/population of the city. More than ten tram lines. Countless number of buses.
majidazimi··on Atom's new concurrency-friendly buffer implementation
Developers want the best quality from other industries, while in the mean time they suggest "Worse is better" for software industry. How about using the same strategy for air crafts, ships, cars, trains, medical devices? Some authority really needs to regulate software industry so every software company builds a high quality, energy efficient, crazy fast software. Aerospace people were successful to land human on moon on 1969. It is late 2017 and software industry is struggling to reduce the memory usage of a text editor to under 1GB. Retarded.
majidazimi··on Atom's new concurrency-friendly buffer implementation
Even hello world programs tend to show different performance characteristics on different OS/platforms. The idea of write once, run everywhere is over. In a moderately complex software, changing the OS/platform is a non trivial problem. Recompiling the code (which is mostly automated) is the least problematic part of it.
majidazimi··on Atom's new concurrency-friendly buffer implementation
It is painful but inevitable. There is no single language that does the garbage collection great on behalf of you. However we are getting closer and closer to find smarter ways to do manual garbage collection.
majidazimi··on Atom's new concurrency-friendly buffer implementation
When they decide to abandon:

1. Dynamic typing

2. Global interpreter lock

3. Automatic garbage collection

4. Interpreting the code (instead of compiling to a single binary).

5. Virtual machine shit

It is just the matter of time, until the team accepts the pain to learn "How to do stuff in C/C++/Rust?".

majidazimi··on Atom's new concurrency-friendly buffer implementation
Sooner or later everything has to become native. JS/Ruby/PHP/... shit is only for initial launch.
majidazimi··on NW.js based operating system
Get ready to replace your PC with a super computer.
majidazimi··on Serverless is cheaper, not simpler
Software RAID is for you. Hardware RAID is only useful if you are buying the high end ones. Other than that software RAID is more flexible and is less susceptible to failure.
majidazimi··on HP Updates Z8 Workstations: Up to 56 Cores, 3 TB RAM, 9 PCIe Slots, 1700W
Atom/Electron devs: Challenge Accepted.
majidazimi··on Reasonable Scala Compiler
I would argue Scala already has all of them but the last one. However there are shit load of absolutely unnecessary features in the language. As the parent link states, twitter just removed shitty features and there you go: An easy to use Object/Functional language which runs fast and has awesome concurrency features.
majidazimi··on Reasonable Scala Compiler
This truly means we still lack a programming language with:

    1. reasonable support of object oriented programming.
    2. reasonable support of functional programming.
    3. solid concurrency features.
    4. runs comparable to native code.
    5. simple to learn.
Even though it is not difficult to create such a language but we see a new language poping out every now and then and none of them try to solve these issues.
majidazimi··on Intel Reveals Post-8th Gen. Core Architecture 10nm+ Ice Lake
Hmmm. It seems Atom/Electron devs need to work hard to slow down new generation processors...
majidazimi··on Ask a Female Engineer: Thoughts on the Google Memo
That's not because women are incompetent. It's because the workplace is putting so much pressure on engineers that even some men prefer to be promoted to management level after a decade of technical work.
majidazimi··on [dead]
Then the better solution would be not up vote it at all rather than puting a flag on it that this is bullshit.
majidazimi··on [dead]
Yeah, Google staff are trying really hard...
majidazimi··on [dead]
Probably Google engineers are down voting whatever they see about it. :))
majidazimi··on Why Germans pay cash for almost everything
I think tax is the killing factor. Most of small shops don't want to reveal how much they earn, thus resisting against electronic payments.
majidazimi··on B2fJ – A Java Virtual Machine to run on the 8-bit home computers of the 80s
In the mean time, I'm struggling to open Atom on an i7 processor with 16GB of memory.
majidazimi··on IBM z14 mainframe
No matter how much memory you have, chrome will find a way to consume it.
majidazimi··on Bitcoin study: Period of exclusivity encourages early adopters
And it also gives power to drug dealers, child porn websites, illegal workers to escape tax system, ...
majidazimi··on How Discord Scaled Elixir to 5M Concurrent Users
> Moving web sockets elsewhere are pretty simple regardless of whether you're using Erlang/OTP or not because it's a frontal layer.

It is supposed to be easy. But they are not using language agnostic messaging. Instead they rely on Erlang distribution protocol. This is what makes it difficult to integrate.

> what would be the purpose behind that decision?

1. To achieve composability. I can replace one web socket server with a C++ implementation to see if I can handle 10 million connections per server. If I fucked it up return back to Erlang implementation otherwise fuck BEAM. I'm moving to native code. The beauty of it is that I can do it one step at a time. Even I can implement web socket layer in multiple languages and experiment all possible options in production and no one even notices it.

2. I don't have to pay for 20 Erlang guys who are mostly senior devs. Get 5 of them to write the core and the rest of the team NodeJS guys.

majidazimi··on How Discord Scaled Elixir to 5M Concurrent Users
Consider for some reason (either technical or political), this company decides to migrate their web socket servers to Akka/Rust/Go/NodeJS. Integrating these new servers into their core cluster is going to be deadly painful. They rely heavily on Erlang/OTP internal clustering. This is not even considered as a challenge in distributed systems but still really painful to implement because of their design decision. This is what they did wrong. Clustering and message routing part of the application should be technology agnostic.
majidazimi··on How Discord Scaled Elixir to 5M Concurrent Users
I did also mention that for fast time to market it is indeed a good idea to use already available tools. By the way writing a distribution layer is not that difficult. Many companies/startups with scalable back-ends that are not using Erlang/OTP have already done it. The point is scalable software requires knowledge and Erlang/OTP is not going to magically solve it. But it seems many fans are trying to promote it such that it is a magic tool that is going to make a shit software become a hyper scalable one. Just look at the comments below that how people have gone crazy.
majidazimi··on How Discord Scaled Elixir to 5M Concurrent Users
> You're going to have the same questions with any other language too. Very few companies get to write clients, servers, and everything else in one language that never updates.

Then I don't see much difference between Go, Java, ... vs Erlang except they are simpler to learn plus finding Java, NodeJS, ... devs is much easier. What was the point of using Erlang? It was supposed to solve a problem for us, but we end up of solving the problem ourselves.

What I'm really trying to say is: integrating a mainstream language like Go, Java, C++, ... with a messaging layer like ZeroMQ (or something else) and adding some reliability features is going to be easier than introducing a totally new language (with a totally different paradigm) into the stack.

majidazimi··on How Discord Scaled Elixir to 5M Concurrent Users
It's great that they support C and JVM stack. But for other major platforms such as NodeJS, Go, ... we still need to approach the goal with some C extensions integrated in both platforms. Erlang/OTP distribution/clustering is really not designed for heterogeneous environment which is fine, since it is used in telecom industry with nice commercial support contracts backed by Ericsson. However I don't consider it as an amazing piece of engineering from a perspective of a system designer who is dealing with many teams with different language/stack preferences.
majidazimi··on How Discord Scaled Elixir to 5M Concurrent Users
> 1) Better to have primitives that scale you to X rather than having to get to X on your own.

For a fast time to market, I do agree with you. But if you are well established company in the market, then in most cases "do it yourself" is the best idea. Unless you have the money to call for experts to fix the problem for you.

> 2) The grand parent wrote the Elixir language.

I didn't know him, nor I care.

> 3) Making sweeping like "A better architecture for a distributed system has a strong composability property" is very easy.

I'm considering this as an excuse, than a technical argument.

majidazimi··on How Discord Scaled Elixir to 5M Concurrent Users
What difference does it make? Erlang/OTP distribution doesn't have pluggable architecture. Sooner or later you will reach a point that you have to modify it. Then you are diverging from the original branch which makes it even more difficult to maintain it. You have to merge your additions into every release (minor or major) and test it thoroughly.

A better architecture for a distributed system has a strong composability property. It should be possible to modify every possible aspect of it on a running cluster without introducing downtime.

Write your own standard well documented distribution layer and become independent of underlying technologies.

majidazimi··on How Discord Scaled Elixir to 5M Concurrent Users
It seems awkward to me. What if Erlang/OTP team can not guarantee message serialization compatibility across a major release? How you are going to upgrade a cluster one node at a time? What if you want to communicate with other platforms? How you are going to modify distribution protocol on a running cluster without downtime?

As soon as you introduce standard message format, then all nice features such as built-in distribution, automatic reconnect, ... are almost useless. You have to do all these manually. May be I'm missing something. Correct me if I'm wrong.

For a fast time to market it seems quite nice approach. But for a long running maintainable back-end it not enough.

majidazimi··on Delivering Billions of Messages Exactly Once
What is so exciting about this? There is still possibility of duplicates. You still have to put the engineering effort to deal with duplicates end-to-end. If the code is there to deal with duplicates end-to-end, then does it really matter to have 5 duplicates or 35? Or may be they just did it to add some useful cool-tech in to CV?
majidazimi··on Ask HN: What is wrong with 1$ subscription license for open source softwares?
Then how Spotify collects 10$ per month? Register user with email and get her credit card number. Ban temporary email providers. After trail period start charging. For enterprises charge company for a batch of registrations. I'm just curious to know why it is difficult.
← PreviousPage 5 of 6Next →