Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
silentbicycle
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
13 ms
·
91.
▲
by
silentbicycle
13y ago
Garbage collection is a particularly cross-cutting implementation issue, and tends to interfere with all kinds of abstraction. You're essentially making a system that knows which specific ways abstraction can be broken safely, so that
92.
▲
Reducing Developer Friction on Embedded Projects
(spin.atomicobject.com)
2 points
by
silentbicycle
13y ago
|
0 comments
93.
▲
by
silentbicycle
13y ago
Lua has access to the filesystem, but you probably want the luafilesystem module for general scripting, it provides more POSIX and Windows-specific functionality. As a general rule, the Lua standard library only includes what can be portabl
94.
▲
Knocking Out Bugs with greatest (C unit testing)
(spin.atomicobject.com)
4 points
by
silentbicycle
13y ago
|
0 comments
95.
▲
by
silentbicycle
13y ago
As Scott Locklin said in a parallel comment, J already comes with excellent documentation and tutorials. This would be a better starting place: http://www.jsoftware.com/jwiki/FrontPage As a language, J isn't ever
96.
▲
by
silentbicycle
13y ago
You'd be surprised. I'm more familiar with k (kona) than J, but many of those seemingly inscrutable blocks of punctuation become recognizable as a unit pretty quickly. You can, of course, break huge expressions like that apart and
97.
▲
by
silentbicycle
13y ago
I saw a patch he wrote for copying coroutines, for those who miss multi-shot continuations.
98.
▲
by
silentbicycle
13y ago
Lua has always supported integers, as a compile time setting. Instead of having a full numeric tower, it has a LUA_NUMBER type that can be changed (doubles, by default), and also makes adding new numeric types at runtime (such as libGMP big
99.
▲
by
silentbicycle
13y ago
Thanks. :) I'm still mostly using Lua 5.1.4 most of the time, and I forgot to include that.
100.
▲
A Field Guide to Lua Coroutines
(spin.atomicobject.com)
54 points
by
silentbicycle
13y ago
|
7 comments
101.
▲
Rust Gets a Lot of Things Right
(spin.atomicobject.com)
3 points
by
silentbicycle
13y ago
|
2 comments
102.
▲
by
silentbicycle
13y ago
I agree, they're tricky. I'm currently working on a blog post about them. :)
103.
▲
by
silentbicycle
13y ago
This is a good start, but there's also some deeper ideas in Lua. It has a good implementation of coroutines, for example; if you're familiar with continuations from Scheme, they fit most of the same uses. (They're like genera
104.
▲
by
silentbicycle
13y ago
Part 1 of the post ( http://spin.atomicobject.com/2013/05/02/chicken-scheme-part-... ) focused on CHICKEN, this one focuses on SPOCK, a Scheme that compiles to JavaScript.
105.
▲
Behind the Scenes with Chicken Scheme and Spock (Part 2)
(spin.atomicobject.com)
30 points
by
silentbicycle
13y ago
|
3 comments
106.
▲
by
silentbicycle
13y ago
I wrote a similar tool to this in C, ff ( https://github.com/silentbicycle/ff ). The main difference is that, where `ffind foo` appears to be comparable to find . -name "*foo*" , ff is closer to
107.
▲
by
silentbicycle
13y ago
I've had and enjoyed both. The latter has less about the fundamentals, but adds chapters on real-time GCs, concurrent GCs, and other advanced material. (Most of whose research probably came out after the first edition.) If you're interested
108.
▲
by
silentbicycle
13y ago
My focus on licenses so far only really concerns making it easier for vendors like the OEM to use my library. When I open-source hardware layouts, I now know I need to investigate license details for hardware-specific language. (I don't hav
109.
▲
by
silentbicycle
13y ago
If you have any other recommendations for making this process smoother, please let me know. I want people in your situation to be able to use my libraries without these irritations. (Author of the post.)
110.
▲
by
silentbicycle
13y ago
The MIT, ISC, and zlib do not seem to, and the OEM is happy with the ISC. I didn't check the GPL, because its overall design conflicts with my intent. Here's the ISC license, in its entirety: Permission to use, copy, modify, and/or di
111.
▲
by
silentbicycle
13y ago
I probably cannot discuss the specifics of the vendor, but I don't know if First Sale applies in their country. I'm not a lawyer, and their lawyers brought it up as a potential issue, so I'm inclined to take it at face value.
112.
▲
by
silentbicycle
13y ago
The "public domain" designation has its own problems, nicely summarized on Google Code ( https://code.google.com/p/support/wiki/FAQ#Can_I_host_code_t... ). In particular, Dr. Richard Hipp (SQLite's main author) has talked about problems tha
113.
▲
by
silentbicycle
13y ago
It was never my intention that people who use my open-source library complicate their supply chain by pushing additional work onto their customers. The paperwork wouldn't necessarily just mean slapping a post-it™ note on the product, it c
114.
▲
by
silentbicycle
13y ago
It is straightforward if you read the license closely with hardware in mind , but I've been releasing stuff under the BSD license for much longer than I've been doing embedded development. I thought I knew what the BSD license meant, but m
115.
▲
by
silentbicycle
13y ago
Author here. I don't think the BSD license is broken, just that the legal implications of that clause were surprising to me, and I thought I'd share what I learned. I'm still likely to use the BSD license in other contexts, but will probabl
116.
▲
Why a BSD License Might be Wrong for your Embedded Open-Source Project
(spin.atomicobject.com)
36 points
by
silentbicycle
13y ago
|
39 comments
117.
▲
AVR-based FM-transmitter
(spritesmods.com)
2 points
by
silentbicycle
13y ago
|
0 comments
118.
▲
by
silentbicycle
13y ago
A tenth of a second seems to be a common threshold for how long something can take before it becomes a noticeable delay. (I've seen 75 - 200 msec in UI literature.)
119.
▲
by
silentbicycle
13y ago
I use lua for that, and it seems to be a very good fit. There's awk influence in its history, so it's probably no accident.
120.
▲
by
silentbicycle
13y ago
I had to implement my own malloc/free/etc. on an embedded project recently, due to a lack of thread-safety in the vendor's C stdlib * . I wrote a blog post about it ( http://spin.atomicobject.com/2013/04/17/embedded-memory-unde... ), with a
More ›