acidtrucks

For me, it was growing up with Sonic the hedgehog. I was trained that keeping as many rings as I could would ensure my survival.

Indeed. The first step is commoditizing and genericizing mobile hardware, like what happened to the PC market in the 80s. Purism is taking a big leap at this, and I definitely want to encourage that.

You don't have to call it giving up. Go is pretty easy to pick up if you're used to high level languages. I would recommend reading a pretty short book called "concurrency in go" (Katherine Cox-Buday) for some really concise education on it.

I wish x509 certificates had several CA signings. I would feel better n times better about a peer who has n unique validations.

Every new CA that gets included just amplifies opportunities for coercion and blunder.

It does pose a significant problem.

I see more value in it for clear technical tasks with technical descriptions, and not so much for discussions. Then proposals can be peer-reviewed before accepted as work that needs to be done (as a merge request to master, for example).

Then another problem that comes along with that, especially for golang users, is that your master branch is getting bombarded with issue updates, causing what looks like releases, when there's no effective change.

IMO It should be feasible to build data bridges for integrating or syncing with related systems.

That said, as a developer I'd love it if I could track my more technical thoughts & needs without having to go to my enterprise tools where BA's run wild & confused. The trade-off of course being more dissonance and potentially a failure to advocate for this work in planning, unless you synchronize data somehow.

I love this because I started building a small utility to help me consistently track issues inside my project files like tickets/{folders}/{file }.md inside my projects, because I do not need an enterprise level management system, and I also really like the idea of tickets moving and closing as a part of merges, IMO it provides a better context when looking through history.

This is clearly more elegant, though it adds a new dependency, which is OK.

Thanks, I literally just came here to ask for book recommendations on this topic.

Are there any other suggestions?

I agree with this, and I would also like to see more welfare programs separate from the insurance role. Insurance companies like to trick you into thinking you're getting a better deal because of them. That's not what insurance means. Keep those roles separate and straightforward.

Are Canadian vpn services subject to NN regulations?

I would rather have a larger handheld device than my Nexus 5x if it meant I control the hardware and software on it. 2/3/4 I think can be worked out by the consumer market as long as standards can be crafted for modularity.

I would love to see a company whose business model is making generic and standard consumer electronics parts that are small and powerful, with options to boot. I would love it if I could build & maintain my own mobile computer (AKA smartphone) just as I would build my own PC. Since taking my kindle voyage apart, I realize that this must be very doable. That thing is way less sophisticated than a raspberry pi, it just happens to be a form factor that I like to hold.

We're returning to the days of booting directly to you application, like we did with apple II

Is it common for companies to ban LGPL?

Maybe this is terrible. Maybe this is the beginning of something totally new. There is nothing about WWW that prevents us from using totally different technologies, other than being really pretty good.

I've always wanted to run openmoko. If I could run it on modern phones and replace android, I totally would.

This is great, but google doesn't need to eavesdrop on us when they compel us to use their avenues for our every action.