You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Hologram is a cellular platform designed for the Internet of Things. Thousands of connectivity teams rely on Hologram to keep their fleets connected around the world — from Burbank to Brisbane. Hologram was founded in 2014 by Benjamin Forgan and Patrick Wilbur. Inspired by the connectivity challenges affecting food delivery startups in Singapore, Hologram's co-founders focused their efforts on removing the red tape preventing fast-growing IoT teams from launching cellular equipped fleets around the world. What started as a Kickstarter, under Hologram's old name, Konekt, has blossomed into the de facto networks IoT teams use to launch their products. In the years since Hologram was founded, the company has been a partner to leading technology pioneers around the world. Hologram made it possibl
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I bought M1 MacBook Air. It is the fastest computer I have, and I have been a
GNOME/GNU/Linux user for long time. It is obvious conclusion that I need
practical Linux desktop environment on Apple
Silicon.
Fortunately, Linux already works on Apple Silicon/M1. But how practical is it?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Probably not the most poetic nor academic or well written phrase, but let me express in plain English why I end up choosing Functional Programming.
Over my time coding (which I have to clarify that has been short) I have learned two important things about code. (mostly from the experience of many more veteran colleagues)
The best line of code is the one that is not written. Why? Because, every single line of code that you write is instant technical debt.
No matter, how well done it is, how well designed it was, how much of 1000x programmer you are, all the code is debt.
All the code will become obsolete at some point in time, all the code has to be refactored.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Rust maintainer perfectionism, or, the tragedy of Alacritty
I did not submit this to Hacker News and did not intend that this post would have high circulation but have no real problem with it being there or with it having such. I have more recent comments below. This post is from January 2020 and predates the Modular Font Editor K (MFEK) project.
I have not worked on Rust projects in quite a while, and don't know if I ever will again. I feel many crate maintainers are way too perfectionist, for example, despite all the developer hours that went into this PR, it took the effort within years to be (halfway) merged.
There's always a reason not to merge, isn't there? It would be better done with a new nightly language feature, or the function signature should have a where clause, or the documentation is not perfect. There's always a new nit to pick in the world of Ru