-
I need to look at the open source options. Back when Shwartz was the Sun CEO and I was a Java fanboy, when I wanted to make a cross-platform, easy to install GUI application, my choice was obvious. Swing is still my favorite widget toolkit.
One time I tried to make a GUI app in F#, only to discover that even VisualStudio didn’t have real integration with GUI building tools for it. I haven’t tried since then, but if I can get it to work with Mono, I guess I’ll be happy.
-
-
-
-
Yes, you can definitely package anything together so that the user doesn’t have to install any dependencies by hand, but… If you are making a small app, making a package many megabytes in size is likely to just scare Windows people off. UNIX people are unlikely to be fascinated by the prospect of installing a .Net implementation for dependencies just for one app (or even installing it at all), but at least most of them understand the why’s.
-
-
-
-
-
IMO this is not a very good assessment. Mentioning glade#? GTK# may not be dead, but AFAIK glade# is.
-
why link to undeadly instead of directly to the tutorial? https://github.com/bob-beck/libtls/blob/master/TUTORIAL.md
-
-
This seems kind of old. Do all of the limitations of QT still apply?
-
There is an case of
let () = print_endline hishould belet () = print_endline hello -
-
no mention of ropes?
-
That’s a newer thing popularized in the Xi project. Most text editors didn’t use them per comments in the last discussion.
-
-
I’d never heard of “snap” before, and I’m not sure I understand what it’s trying to do. Is it just a lazy way to publish closed source software on Linux? I really don’t see why I’d choose a snap over using my regular package manager.
-
Yes and no. Snaps are the last of many tries to have a single, uniform package format among a lot of different Linux distributions. They can be installed on *buntu, debian, arch, fedora, opensuse, …. They also offer built-in sandbox.
You are correct that a lot of propritiatory software is using it to distribute packages because it saves some time, but that’s not the main goal of the format.
-
Snaps are the last of many tries to have a single, uniform package format among a lot of different Linux distributions.
Unfortunately, there are at least three competing standards (Snap, Flatpak, AppImage). However, Flatpak seems to be supported in more distributions than Snap:
https://kamikazow.wordpress.com/2018/06/08/adoption-of-flatpak-vs-snap-2018-edition/
Regardless of what one thinks of such formats, they have already lead to interesting phenomena. Flatpak is, for instance, quite popular among pirates who use it to pack Windows games with a custom Wine configuration:
Then there is the Winepak project, which packages redistributable Windows software:
-
-
There is some strange things about snap: https://medium.com/@acam/im-afraid-for-the-future-of-ubuntu-2f41796073b2
-
-
-
IMO anyone who says flash failed isn’t really paying attn
-
Ubuntu’s blog post says that the images are available on docker hub but I can find no actual evidence of such a thing.
-
“This is the standard Ubuntu 18.04 LTS image on the Docker Hub.”
https://hub.docker.com/r/library/ubuntu/tags/ There it is. 31MB of glory
-
-
-
-
The underlying factor that caused the github purchase to be a problem was that github was free. As long as the service is free, then selling out is always a risk.
Why not take the total server costs at the end of the month, divide by the number of users, and charge that as a monthly subscription to keep the lights on? If the system is even marginally profitable, that makes any kind of selling out (via acquisition or selling user data) less attractive.
If the system is costing the administrators money, then they have a high incentive to sell out.
-
Why not take the total server costs at the end of the month, divide by the number of users, and charge that as a monthly subscription to keep the lights on?
Nah, charge them based on use like in mainframe and cloud models. That’s more fair. Safer, too, for the host. There probably should be a baseline fee that covers administrative overhead or at least contributes something to it. The usage charges go on top of that. There could be some usage that comes with the baseline fee, though.
-
That’s an interesting point, and I’ll have to consider it. Though, I don’t see the user base growing enough to make selling out a possibility. My philosophy is that there should be many services like this one to prevent any one from growing too large and making selling out a possibility (that’s why the goal is to make everything open source - if someone wants to clone Asymptote they have my blessing).
-
-
-
True. In that circumstance I would run a cheap ($2.50/mo) VPS to keep essential services running (such as email) while fundraising.
-
-
-
-
-
Asymptote’s existance isn’t because of fear of what Microsoft might do to GitHub. I made it to test out a midpoint between large, centralized services and everybody self-hosting. I don’t think Microsoft will screw up GitHub, it’s just that the discussion around the purchase prompted this idea.
-
-
-
We can just make sure that the admins publish inappropriate stuff like ‘women are weaker then men’ or ‘women make less money because they make different choices compared to men’ on its blog every month. Then the site would be ‘unbuyable’ because of the outvogue apparent social position of the owners. The people in the know would know to ignore such posts, but the bad-headline potential of these blogs would poison the site against any future buyouts.
-
This is a rather sarcastic way of making a reasonable point - what sorts of rules about host content will Asymptote Club (or other similar “middle-ground” services) enforce, and how resistant will it be to social/political pressure to censor content? What if I want to use Asymptote Club’s gitea/CI service to actively develop machine-learning software that’s illegal in some jurisdictions but not others? What if I want to use their matrix service to host a misogynist chatroom because I believe that the accusations that the content of the chatroom actually constitutes misogyny are complete bullshit? If something hosted on Asymptote Club got into the news and invokes a social media shitstorm against it, how much can I trust that Asymptote Club will keep hosting it, and how much do I have to know about the personal politics of zebMcCorkle in order to ascertain that?
-
-
-
-
Yes, I enjoy it. Since I was 6yo I’ve liked to tell the machine what to do and make it do things.
-
“At the end of the day, nearly all of us run software on the Linux Kernel. The Linux Kernel is written in C, and has no intention of accepting C++ for good reasons. There are alternative kernels in development that use languages other than C such as Fuschia and MirageOS, but none have yet reached the maturity to run production workloads.”
First counter is all the software not running on Linux kernel. Microsoft, Apple, IBM, Unisys, etc still exist with their ecosystems. Second, there’s two things here author is conflating with the C justifications which are too common: effect of legacy development; what happens at a later point. For legacy, the software gets written in one language a long time ago, becomes huge over time, and isn’t rewritten for cost/time/breakage reasons. That’s the OS’s for sure given their size and heritage. Although legacy kernels are in C, much of Windows is in C++ and Mac OS X in Objective-C. They intentionally avoided C for those new things.
Outside those, Burroughs MCP is done in an ALGOL, IBM uses macro-ASM’s + PL/S for some of theirs, and OpenVMS has a macro-asm + BLISS in theirs. Those are still sold commercially and in production. For others in past, there were LISP machines in LISP variants, Modula-2/Oberon systems w/ Astrobe still selling it for microcontrollers, Pascal, FreeBASIC, Prime had a Fortran OS, Ada used from embedded to mainframe OS’s, and several in Rust now. There’s also model of systems stuff in high-level language that depends on tiny amount of low-level stuff done in assembly or low-level language. OS projects were done that way in Haskell and Smalltalk.
Lot of options. You don’t need C for OS’s. The sheer amount of OS work, libraries, compiler optimizations, and documentation make it a good choice. It’s not the only one in widespread use or strictly necessary, though. It’s possible other things will work better for OS developers/users depending on their needs or background.
-
-
True (source: I used to write kernel extensions for macOS to do filesystem things). NeXTStep/OpenStep had Driver Kit, an ObjC framework for writing device drivers in-kernel, which appeared in early Mac OS X developer previews but not in the released system.
Specifically IOKit (the current macOS driver framework) is Embedded C++, which is C++ minus some bits like exceptions.
BTW Cocoa is also a “legacy part”, but it comes from NeXT’s legacy, not Apple’s. IOKit (the C++ driver framework) was new to Mac OS X (it didn’t come from NeXT or Mac OS 8, though clearly it was a thin port of DriverKit) and the xnu kernel was an update of NeXT’s version of CMU Mach 2.5.
-
Yeah, that’s the legacy part. They just keep using what it’s already in. It was the newer stuff like Cocoa that used Objective-C IIRC. I should’ve been more clear.
-
-
It doesn’t at all. I already addressed why the kernel stays in C: someone long ago chose C over the other systems languages with so much code they can’t justify rewriting it. It’s an economic rather than a language effect. Thinking it’s strictly the properties of C is like saying Sun Microsystems wasn’t the cause of the rise of Java, Microsoft wasn’t behind rise of .NET, and so on. People are still being trained in those languages to add to massive codebases that are too big to rewrite. Same thing that always happens.
-
-
-
-
-
In addition to all that, I think the systems level domain also has a new growth sector by replacing the kernel with a hypervisor+library combination. Aka, the topic from this talk[1].
-
Although still listening to talk, their robur collective has a great, landing page. Lots of good stuff on it. I also like her team is working on a home router. That’s what I told separation kernel vendors to build since it’s (a) hugely important, (b) huge market, and (c) can be done incrementally starting with virtualized Linux/BSD.
-
-
-
jrwren
2 months ago
|
link
| on:
Introducing Network.framework: A modern alternative to Sockets - WWDC 2018
its a bummer this isn’t open source so that swift on non-mac platforms can use it.
-
pastebinit for gists? yes plz
-
i remember when the original article was posted and seeing it and just laughing and feeling sorry for the author. Nice to see he has corrected himself.
-
The robots.txt spec does not include it, but most bots support the extension: Crawl-delay
Rather than block bing, they should be adding
Crawl-delay: 10Bing documents this: https://blogs.bing.com/webmaster/2009/08/10/crawl-delay-and-the-bing-crawler-msnbot/ https://blogs.bing.com/webmaster/2008/06/03/robots-exclusion-protocol-joining-together-to-provide-better-documentation
-
-
Is it me, or is 800k lines a lot for any application of this type?
-
jrwren
5 months ago
|
link
| on:
A potential way to have spaces in filenames and not break the Unix command line
There is very little difficult with spaces in filenames. Learn to quote. Learn to escape. Then everything is very easy.
-
-
In that case:
-
The title is incorrect.
-
Still nothing difficult.
make ‘hello world’ g++ “hello world.cpp” -o “hello world”
With a Makefile:
hello\ world: hello\ world.cpp echo match $(CXX) $(CXXFLAGS) "$^" -o "$@"Maybe the OP was making a joke about using UTF8 NBSP and I just didn’t get it.
-
-
-
-
Hail_Spacecake
6 months ago
|
link
| on:
Eric S. Raymond - Re: [Groff] man pages (tangential to Future Redux)
I don’t understand the opposition to this idea. Having command line documentation that opens up a HTML page in a browser is reasonably common. For instance, this is exactly what
rustup docsdoes, which I use all the time. I agree that there’s something to be said for having documentation that is completely console-friendly and has no connection to a graphical screen, but it’s also the case that the entire linux command line ecosystem is old and adheres to a lot of conventions that made sense on machines of ~30-40 years ago (in some cases emulating even older terminals). I think it’s a good thing to consider ways to make the command line experience better by taking advantage of the graphical facilities that even the cheapest general-purpose computers have had for decades now.-
Almost all of my servers are headless, and a bunch of them are in DMZs where they cannot access the internet, and yet I still find myself needing access to the documentation that corresponds exactly to what is installed when I am doing sysadmin stuff fairly frequently. I don’t want to have to install X, a desktop environment, a graphical browser, and open the server up to the internet; to make esr’s suggestion work as he has claimed it is implemented requires all of those things. Also the suggested toolchain seems to be problematically buggy, according to the mailing list replies.
-
-
the problem is deciding on a standard. this proposal is particularly bad because it invites documentation writers to assume their users will have the latest firefox/chrome/ie/safari installed, which kills compatibility with older, lower power computers that still function perfectly fine but for their interaction with the modern web. that is an immediate practical concern, then there is the general principle of code simplicity, which esr seems to be flaunting his defiance of.
-
Or maybe configure loading properly, including failing on unexpected loads early.
Sounds like a good solution if you are looking to optimize your queries. Honestly, we aren’t.
A simple example is a Rest Framework model API. We want to use this API for getting different data fields every time. There is no smartness in the ORM to decide whether to pre-fetch or not. Unless I take time to optimize each of the cases manually (or mindlessly always do JOINs which I don’t need), I can’t make it return me the data in an efficient way.
why aren’t you looking to optimize your queries?