HackerTrans
TopNewTrendsCommentsPastAskShowJobs

liyanage

no profile record

Submissions

LLM Policy for Rust Compiler

github.com
100 points·by liyanage·2 tháng trước·84 comments

Decoding Utility Markings Spray-Painted on City Streets

99percentinvisible.org
2 points·by liyanage·4 năm trước·0 comments

Rule of Silence

linfo.org
34 points·by liyanage·4 năm trước·1 comments

[untitled]

1 points·by liyanage·4 năm trước·0 comments

YubiKey Bio builds biometric authentication into a security key

zdnet.com
2 points·by liyanage·5 năm trước·0 comments

Reminiscences of the VLSI Revolution (2012) [pdf]

ai.eecs.umich.edu
28 points·by liyanage·5 năm trước·1 comments

The Ars Technica semi-scientific guide to Wi-Fi Access Point placement (2020)

arstechnica.com
3 points·by liyanage·5 năm trước·0 comments

United States Frequency Allocations [pdf]

ntia.doc.gov
1 points·by liyanage·5 năm trước·0 comments

Safari 15 Beta Release Notes – Apple Developer Documentation

developer.apple.com
4 points·by liyanage·5 năm trước·1 comments

First NorCal Legoland is about to open with 1M-brick re-creation of the Bay Area

sfgate.com
1 points·by liyanage·5 năm trước·0 comments

The Eudora Email Client Source Code – CHM [2018]

computerhistory.org
2 points·by liyanage·5 năm trước·0 comments

comments

liyanage
·4 năm trước·discuss
Thanks for that link! I just converted it to an Apple Music playlist as well: https://music.apple.com/us/playlist/wipeout-soundtracks-1995...
liyanage
·5 năm trước·discuss
Wow that second link ("Reminiscences of the VLSI Revolution") turned out to be a 29 page rabbit hole providing a fantastic glimpse into the history and early days of chip design and engineering, thanks a lot for posting that! Here's a direct link to the PDF: https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.69...
liyanage
·5 năm trước·discuss
Things like "not sure" and "I think" and "even if I'm wrong" suggests that it is not very clear what is covered and what isn't. A lawyer would probably have to sort that out.

The practical problem is that some organizations simply discourage or don't allow the use of GPLv3 or AGPL software. I don't want to learn one tool for personal projects and another for potential work projects, in case the opportunity comes up.

The easiest way to deal with that is to just switch to a tool that has a license that is more widely accepted.
liyanage
·5 năm trước·discuss
For me it was the license that made me not pick it: https://github.com/getpelican/pelican/issues/1397.

A while ago I was picking a new SSG and I would have preferred something written in Python so I can hack on it more easily. I ended up moving on because of the license.

I am now very happily using Hugo.