ramalama seems to be trying, it's a docker based approach.
1,511 karma · joined May 20, 2010
It seems like an AI would not "play by the rules" and can easily detect weird edge cases and shortcuts. But as far as I can tell from the small GIFs, it's not doing any particular glitches.
I talked to someone who worked on AsicOne, and he said that even if you make your own PDK and draw your own transistors and everything, you'll still have to sign an NDK to do the sign-off and what not. I'm not intimately familiar with the whole process myself, but from what I understand it is basically impossible to have an open source analog design that you can actually manufacture. (sure, you can make a theoretical toy thing, but if you can't manufacture it, who cares?)
Everything else is very experimental at best. These days the FOSS FPGA tools are finally getting some traction, with Yosys and Nextpnr. But AsicOne tried to make an ASIC with open source, and faced endless troubles.
For ASIC there is basically QFlow, which is quite old, but used successfully to tape out a chip in the past, and there is OpenRoads, which is very new, experimental and ambitious. There are still major gaps in these tools, so in the end you inevitably have to sign an NDA and use proprietary tools and libraries.
And that's just talking about DIGITAL semiconductors where you compile HDL to pretty much generate the transistors from foundry cell libraries. So you have to sign an NDA to get the cell library, but you can at least release your code.
For analog chips, you can't do anything. An analog design highly depends on the parameters of the transistors you use, so before you even BEGIN designing, you have to sign an NDA to get the transistor models and you can NEVER open source an analog design.
The small dot of light at the end of the tunnel are projects like Minimal Fab, who make more accessible fabrication lines with open transistor models.
The crazy thing is that back in the days there were lambda rules, which were open rules anyone could use to design and model with. But with sub-micron devices, these scalable rules no longer scale, so fabs started producing secret models for their specific process.
I'm hopeful that after FPGA, and digital ASIC, analog will be next to be revolutionized.
In particular it's hard to tell if any particular fork is just a one man hobby project, a fork of a fork, or has any significant work behind it.
Of course the big one is LineageOS, but they seem to make specific phone images, mostly for high-end phones, rather than generic system images for my low-end phone.
The list of generic system images is extremely long and not all that helpful: https://github.com/phhusson/treble_experimentations/wiki/Gen...
I ended up chosing phh-treble because it doesn't add any BS, promises quick updates, and serves as a base for many other roms, lending it some reliability. It's pretty much AOSP with hardware fixes.
That said, it doesn't do some pretty basic things like automatic brightness and night mode, or a PIN timeout. So maybe that's eventually drive me to try another ROM...
The problem is not which messaging app I want to use, it's which messaging app my friends are using.
That said, if I had to choose, I think Matrix has a slight edge in my books because it's a protocol rather than a silo. Even though Signal is private and open source, they are hostile towards people running their own Signal builds on company servers, and unwilling to federate with other servers.
Essentially, you run the official Signal app on the official Signal servers, or GTFO.
Personally, only Limor Fried. It's weird, but also interesting, that tech is so faceless.
My CPU is very small, (~300 LUT4 on an FPGA using Yosys), but has a very minimal ISA. It's mostly an accumulator machine with a stack pointer.
Looking forward to someone building a larger system with this. Or... a Yosys backend?
This update looks really neat, and may solve some problems for some people. But personally my biggest gripe with Qt is qmake.
When you are doing Android, lots of resources assume Gradle, and lots of Qt stuff assumes qmake. Neither is ideal if you're dealing with other libraries like gstreamer, or even worse: proprietary libraries compiled using an old NDK.
So I ended up writing my whole build system in cmake, which made builds on Windows and Linux a lot saner, but made Android a living hell. I'd love to see better support in Qt for actual sane build systems you can use with real world third-party libraries, because qmake is not it in my experience.
I'm not saying it's fake, but I'd like to know where the data comes from, and how reliable it is.
As far as I know there is only iOS and Android forks. Android forks are an option if your phone supports it, but living without Google Play (Services) limits your app choices a lot.
Windows Phone and Blackberry sadly gave up the battle. Others like Ubuntu phone and Firefox OS never really materialised.
As far as Google Play alternatives go, there is the Amazon store and F-droid, but good luck finding even the most basic Android apps on either.
Honestly, I'd settle for a dumbphone with WhatsApp(extremely widely used here) and a browser. Almost feels like we're coming full-circle to the first iPhone with very few native apps and powerful web app capabilities.