xd1936
Joined 11 years ago
Joined 11 years ago
Several of their new components are just classes, defeating the original purpose and contradicting the vision of Pico.
Why are the first one or two letters in headings wrapped in <em>, like the _Bl_ in "Blades"?
Why are they calling their Pico fork "anyblades/pico", when the original Pico author's post says "The Pico CSS name and logo are not covered by the MIT license. Please give your fork its own name, so users don’t confuse it with the original."?
The worst offender: What is going on with this nonsense: https://blades.dev/css/frameworks/
https://github.com/leoherzog/ParameterPage
https://parameter.page/?title=This%20is%20an%20Example%20Pag...!
> However, the current prototype uses the FPGA to clock the ESP32, which results in poor phase noise.
Looks like this was solved five days ago:
https://github.com/h0m3us3r/eSpDR/commit/41a0ffe279119df942e...
I'm a technology enthusiast living in West Michigan. I currently work at [Hope College](https://hope.edu/directory/people/herzog-leo/) and have enthusiasm for too many things.
I enjoy working with: - Javascript and Google Apps Script - Python - Linux and Raspberry Pis - ESP32/ESP8266 and Arduino - Decentralization and the Distributed Web - Podcast Tools - Social Media APIs - Hardware Diagnosis and Repair - Weather Data - Ham Radio
I'm a learner, teacher, tea enthustast, campfire ukulele player, flag enthusiast, weather spotter, [podcaster](https://spitball.show/), comedy lover, and your friend.
[ my public key: https://keybase.io/leoherzog; my proof: https://keybase.io/leoherzog/sigs/ivrd5z5G9b2x_BZCIkIouM6gl8BMWS_23M_LZYttCfk ]