nrclark

40 ms·

481.
by nrclark 7y ago
That's some crazy shit right there, thanks for telling us about it! For those interested, here's a link that discusses it: https://www.tcl.tk/man/tcl8.6/TclCmd/return.htm
482.
by nrclark 7y ago
Make is great, and I use it all the time for task orchestration. I wouldn't use a hand-written Makefile as the top-level build tool on a library or program - CMake or Autotools is a much better fit there. But on a build that pulls down
483.
by nrclark 7y ago
I do appreciate the intention behind GPLv3. And it does has a lot of good updates over GPLv2. The reason why I said it's impractical to include GPLv3 code in a system that also has secret sauce (maybe a special control loop or some aud
484.
by nrclark 7y ago
The solution that the article authors want is for you to buy their service.
485.
by nrclark 7y ago
Not sure if I agree with the 'Scalable' section of the article. As an embedded Linux developer, I appreciate why a company might want to push updates autonomously to their product. But as a customer, I want to choose when/if
486.
by nrclark 7y ago
When buying smart devices for your home, just remember folks- the 's' in IoT stands for security.
487.
by nrclark 7y ago
Specifically GPLv3 is the sticking point - not the GPL in general. GPLv2 is a great license, and I use it for a lot of tools that I write. That's the license that the Linux kernel uses. GPLv3 (which was written in 2007) has much toughe
488.
by nrclark 7y ago
Can confirm. GNU awk is GPLv3, which means it can't be legally included on any system that prevents a user from modifying the installed firmware. This is a result of GPLv3's "Installation Instructions" requirement. Every
489.
by nrclark 7y ago
libtoolize is a program provided by the libtool package. It's pretty common in the GNU ecosystem, and is used for managing some of the more subtle aspects of build-time and runtime linking. Agreed that the README needs much better docu
490.
by nrclark 7y ago
My phrasing was a little ambiguous maybe. What I meant was that the regular `make` package from most distros isn't compiled with support for Guile. So _distros_ are the ones that aren't adopting it. Make's Guile extensions wi
491.
by nrclark 7y ago
I had the same experience. I think the slow adoption of Make's Guile extension is precisely because of its larger dependency load. If Guile had the same set of dependencies as GNU Make, I bet we'd see more distros turn it on by de
492.
by nrclark 7y ago
Excited by the new release. I learned a little bit of Guile for scripting in Make, and I dig it. It's a little hard to include in my own designs though, as much as I'd like to do it. If I had a wish-list, it would be: - Make some
493.
by nrclark 7y ago
This is very exciting! Especially the SPICE model library. Microcap's libraries have lots of SPICE models that I haven't seen anywhere else. Being able to grab them will be awesome, even if I wind up using them with LTSPICE.
494.
by nrclark 7y ago
I don't consider myself in a position to judge the validity of anybody's religion. But I'd ask you this - if a religion's values are good, its practitioners are happy and its role in the community is positive, does it re
495.
by nrclark 7y ago
If somebody is targeting inter-Unix builds, Autotools is probably a better pick than hand-rolling a Makefile. But realistically, Linux has captured 75% or more of the entire *nix market. A lot of developers spend their entire careers in Lin
496.
by nrclark 7y ago
Agreed with this. There's one extra dimension though - the toolchain. The catch with MacPorts and Homebrew is that both of them use the XCode toolchain for compilation and linking. And Apple encumbers the heck out of XCode with EULAs,
497.
by nrclark 7y ago
Agreed that a pure Make approach is less than ideal for new software projects. It's great as an orchestration tool though. I use Make for all kinds of wrappers, because it gives built-in dependency ordering and tab-completion. Make is
498.
by nrclark 7y ago
Good point!
499.
by nrclark 7y ago
System76, Asus, etc. don't run afoul of GPLv3 because they don't restrict what you can install. Most Android devices also don't violate any GPLv3 licenses, because they don't include any GPLv3 software. GPLv2 software li
500.
by nrclark 7y ago
The Tivoization clause applies to hardware vendors, with hardware covered by GPLv3's definition of a "User Product". Ubuntu itself isn't a valid comparison, because it's not a physical product. And computers that sh
501.
by nrclark 7y ago
It actually is correct, I think. If you're selling hardware that ships with any GPLv3 software of any kind, the license requires that you don't restrict users from installing their own OS if they want. This was intended as a worka
502.
by nrclark 7y ago
You're right, of course - I wouldn't say that Yocto's SDK generator is perfect. But it does work fine, and you can install the SDK anywhere you want. From a CI system's point of view, what's the logical difference b
503.
by nrclark 7y ago
Gun ownership doesn't help public safety anywhere near as much as you think. The number one and number two uses of guns inside a home are suicide and murder of a loved one, respectively. Defending against a home invader is statisticall
504.
by nrclark 7y ago
If you find yourself wrestling with this in the future, you might try experimenting with Yocto's SDK generation capabilities. Most image recipes have a 'populate_sdk' task that will generate a self-extracting shell script tha
505.
by nrclark 7y ago
Fedora on ARM definitely works better than Yocto out-of-the-box. It's also much larger, and you don't have much control over the core components. You don't have control over how the packages were compiled, and you'd have
506.
by nrclark 7y ago
Thanks to the Yocto team for a great release. I'm excited to start playing with the new hash-equivalency support, which is the biggest addition in this release IMO. Keep up the good work! Yocto is an amazing project, and I'm a hea
507.
by nrclark 7y ago
I work with Yocto in my day job. The learning curve is really steep, but I actually like it a lot. Buildroot a great project with clear goals and good execution. Yocto is flexible to a fault, which makes it a lot more complex. But with that
508.
by nrclark 7y ago
I think the newsworthy part of all that wasn't the physics involved, but more the design-choices on the Rpi 2. Putting a light-sensitive chip (I think it was a wafer-scale package with no casing) on a board that's intended for use
509.
by nrclark 7y ago
I think that people hate on chiropractors _because_ of the pseudo-science aspects. There also isn't much science -even empirical studies- that back up the claims of chiropractic (which doesn't have a noun form of the word for what
510.
by nrclark 7y ago
USB-C is a train-wreck for those of us who work in electronics design. USB-C's chipset support isn't all that good, it seems like. With USB 3 type A, you pretty-much just run your USB lines to the ports on your CPU. Simple, straig

More ›