skysight-inc/HackerNews huggingface dataset:
The architecture he describes, that of an event broker, sounds a lot more like Upstart than it does like systemd, though.

That said, the proposed idea doesn't sound like something that is trivial at all, but rather pretty bug-prone. There already are de facto event engines for certain areas like device hotplugging (formerly HAL and now udev on Linux, devd on FreeBSD), whereas for a lot of other events in Linux software a typical way is to subscribe on an application's D-Bus interface and wait for signals.

Indeed, OS X's notify API looks precisely like a message queue from my brief observations.

But then there's certain events and classes of events (such as "network is up/network is down") that could have literally over a dozen meanings. I'm not sure how a practical centralized event broker could be anything more than a glorified message bus? Otherwise, encapsulating highly multi-faceted and non-deterministic system states into generic events sounds like bugs galore.
Mysterious glowworm found in Peruvian rainforest
Galaxies may be aligned across 1B light-years
No?

Then why does your company employ you? Are they doing charity?
While Git itself might not be the right thing, the principles behind it may well be. You might like to check out Irmin, a library to build distributed storage systems.

http://openmirage.org/blog/introducing-irmin
I'll ping you on gh
Show HN: Tombstone-py: A python module to help you remove dead code
The Best Business Leaders Are Visible at the Front
No, that there is a broad systemic problem doesn't mean that tech doesn't also have specific problems. And even if the problems were only endemic, it doesn't mean that we can't make a difference in tech by acting in tech.

See, for example, this HBR report:

http://documents.library.nsf.gov/edocs/HD6060-.A84-2008-PDF-...

Chapter 8, "Unnecessary Losses", in particular documents that there is a specific problem in high tech.

> That says much more about you than it says about me.

Sure, it says I've been participating in Hacker News discussions on sexism for the last few years, where there has been an overabundance of anonymous dudes who just happen to be vehemently opposed to anything that might reduce the advantages they have now.
It's hard to say, the paper is really long and it's full of mathematical notation that is hard to digest and there are no examples to make it easier. Or, if they are, they are for a symbolic lambda calculus program.

The problem with this kind of papers is that they are for a hypothetic programming language based on lambda calculus. In Ruby we have objects, instance variables and blocks. We have inheritance and modules. It's hard to make a 1-1 mapping between the paper and the real language. This is why Matz said (if I remember correctly) that the algorithm would need to be adapted to an object oriented language like Ruby (so you can imagine, the paper doesn't even deal with objects, probably just functions!).

Before developing Crystal we read some papers, but all of them were pretty limited (they only dealt with primitive types like int and float). We had to think of a new algorithm that adapted well to all of the language features. And the algorithm is very specific to the language, which is something good because we can make it optimal, instead of for a general language.

It's hard to describe the algorithm in detail. We'll eventually do so in blog posts.
Make a beautiful laser-cut enclosure for your Arduino using this ruby gem
Settling in Tibet required a Western import
What the Father of Lean Startup Thinks You Need to Start Up
You "BSD devil" trolls are really not putting in much effort.
A Sign the Startup Bubble Is Maxed Out: It Resorts to Junk Mail to Disrupt
I don't think that's entirely true. I've been told you can get support for older RedHat point releases but you have to pay RedHat an obscene amount of money.
Wrong BSD. And it still wouldn't matter anyway.
I came up with such a format (called BML) and for the same reasons. Here's an example that shows the entirety of the syntax:

server
path: /core/www/
host: example.com
port: 80
service: true
proxy
host: proxy.example.com
port: 8080
authentication: plain
description
:Primary web-facing server
:Provides commerce-related functionality

server
...
proxy host="proxy.example.com" port="8080"
authentication: plain

Everything is a node, which can have a data value and zero or more child nodes. Nesting is determined by counting the number of indentions. It uses a counter so that if you want indents to be one tab, or two spaces, or four spaces, it will still work. (Being too rigid here makes the syntax very unfun for humans to write.)

Once parsed, element-style (first proxy node) or attribute-style (second proxy node) become identical nodes and are treated the same (but with a flag in case you want to write out a modified file): they are fully interchangeable, so no attribute vs element debates, just use what works best for readability. (This really is critical. Some document types would be ten times as long without attribute-style nodes.)

The syntax has no entities. foo="data" can capture any data that doesn't need quotes or newlines. foo: can capture any data that doesn't need a newline. foo\n:data\n:data can capture any data that doesn't need binary. foo\n:base64\n:base64 can capture absolutely anything.

Node names must be [A-Za-z0-9-.]{1,}, and are case-sensitive. The same node name can appear multiple times at any level, even at the root level. Ambiguity is resolved by the order of appearance for each node.

The data values of nodes are completely unparsed by the markup. The syntax knows no difference between strings, integers, floats, booleans, binary data, arrays, etc. The application parses the text however it wants. The library adds some convenience functions (.text() to strip surrounding whitespace, .integer() to get a number, .boolean() to decode true/yes/on vs false/no/off, etc.)

File format is mandatory UTF-8 (no BOM.) Preferred line feeds are '\n', but '\r\n' is also permitted because Microsoft.

The implementation in C is about 8KB. Since everything has a marker, allocations are not necessary for the node names/values (but you will need to allocate the tree structure, obviously.) There's an accompanying path query syntax (ala XPath) that's another 6KB of code or so.

(All the edge cases are well-defined (mismatched indentation, mixing multi-line and child nodes, etc), but the post is getting a bit long.)

This was the best I could do at minimalism. Removing any functionality it has results in ruling out many use cases.
The maximum theoretical efficiency of any battery is 100%. This one is no different.

What you are missing is that while the electricity generator has a maximal efficiency that is smaller than 1, the thermal pump has a greater than 1 efficiency. Multiplied, they are always 1.
Perhaps I should have said 'something like' and qualified the differences.

I'm sure the BSD community can learn and can improve on the idea. Perhaps their result could be ported back to Linux as an alternative.
Ah, very good point - its probably not clear what is and isn't clickable. Thank you for the suggestion
They were suggesting an api for it as well. Who cares what the format is if you access it programmatically?
If that pumped gravel heat exchanger works that well, why don't they create phase change reservoirs and save most of their capital costs?
I'm curious to know what kind of leverage he had over the distros where it wasn't just "ask". Any suggestions on where I can find some info?
To be fair, Beacon gangs its units -- you wouldn't have a single 25 kWh module, but an installation of them. The company's demonstration project is a 20 MW capacity plant with 200 flywheels.

http://www.energycentral.com/generationstorage/energystorage...

The other factor is that when you're operating at grid scale, it's overall changes to the grid flow that you're concerned with. A large city might have a peak load of 2000 MW, and the plant here could handle a fluctuation of 10% -- given the law of large numbers, that's a lot. Sure, you might be turning on a slew of light banks in any given period, but someone somewhere else could be cycling down a cooling plant, or resistance heater, or the like.

I suspect large rapidly cycling loads might also be at issue -- with electrified transit, light rail and trolley buses make high instant demands on the grid, and then return energy through regenerative braking. I don't know how such loads are managed, but they're substantial and I do know that utilities tend to segregate these from other residential and commercial circuits.
Hey guys! This is the first draft of the site :) Please apply to become gigsters if you haven't we absolutely value ability over prestige. Sorry if we communicated otherwise! We just needed a quick way to demonstrate the strength of the initial gigsters. Once again look forward to seeing you guys signup and thanks for the comments...we are still learning! :)
The whole premise behind introducing Phi to compete with discrete GPUs from NVIDIA/AMD was to have a plug-in accelerator which supports x86 which meant no code porting needed, hence enabling companies with millions of man hours invested in their code to simply take benefit of the accelerator. However, this is not the case -- The price/performance ratio for code which is not optimized to make use of massively parallel processors would be mediocre at best.

Besides, Xeon Phi's are reincarnation of project Larrabe which never took off.

If you have to end up optimizing your code for accelerators in any case, x86 or not -- you are better off optimizing it for GPUs instead.
No, secrecy isn't the basis. The basis of representative democracy is transparency so the citizens can judge how well their elected do their jobs. If the elected do what ever they do in secrecy there can't be any fair elections.
These 'types' exist only to allow academia administrivia to be more open for profit. There is not such a thing as a 'manager type of personality', or 'a tech type' - this is an invention, utterly arbitrary, and a product of a corrupt education system that allows such a mythos to occur in order to cater to industrialization of human economy.
The difference is a PC is an open and well documented platform that anyone can write software for. This board and other embedded devices typically don't provide the details needed to implement alternative firmwares. That is the difference between windows on a PC and firmware on an embedded device.
How to Ship an F1 Car Across the Globe in 36 Hours
I think we've finally run out of reply depth (and you've run out of excuses) but the answer is: whatever the market decides. I've decided I want to sell my share. I now have to find someone willing to buy it. The spread alone guarantees I'm not going to get $1 for it.

> I've always referred to market cap, never accounting.

Not true. Which is why my next test question was going to be: the company went public at $10 last year before dropping to $1. So there's $190 in shareholder's equity against 100 shares and $90 cash on hand. Market opens, what's the price?

The core flaw of your argument is that the company can't control the market price. So there's no such thing as a "neutral market cap" transaction that changes the number of shares and you certainly can't "undo" it just because the numbers line up on the balance sheet. Specific to your core error, look up P/B ratio.

This whole thread apparently got linked from elsewhere and "We've limited requests for this url" is the error given. It's been fun guest lecturing here but I believe our overlords signaled that it's time to free up resources.

For anyone who's followed this long, read "Security Analysis" by Benjamin Graham for real insights instead of this incomplete thought experiment gone awry.
The most intriguing part of FreeBSD (any BSD really) from an outsider's perspective I find the fact that "the FreeBSD project" has a bigger, more directed scope than "the Linux project" or "the GNU project". It's a kernel and userland all in one, and they can actually decide to focus more on unity of configuration files and mobility. I get the impression that you cannot decide that as efficiently on Linux at all.

People often say "Linux is all about choice" as if it's a good thing [1]. I think this overwhelming focus on choice really is what's so frustrating about Linux and its community. If needs aren't being catered to, or if there are disagreements, the amount of vitriol that gets thrown around is despicable. The systemd controversy is so terribly shameful, but lo and behold: FreeBSD now seems to be envious of it (or at least some of its aspects). Gnome 3 is widely regarded [2] as the best, well-integrated desktop environment Linux has ever had, and look at the amount of vitriol that got for having a direction and making choices for the user. I personally think that the level of integration systemd and Gnome 3 are attempting to pioneer make Linux far more attractive than ever, but the Linux community really alienates me with its attitude towards that. With this attitude, desktop Linux mostly remains a patched together collection of software. The rough edges of this patchwork are still far more apparent on even the best regarded distros when compared to OS X or Windows or even Android.

It's a shame FreeBSD doesn't maintain an integrated or official graphical interface. Since it uses the same not-so-well integrated desktops as Linux does, it unfortunately means that using FreeBSD is only a minor improvement over Linux for me in daily use [3]. That means I'll just leave it to Apple to build me a well-working and well-integrated operating system. If an operating system project or vendor makes choices for me, I consider that a big advantage most of the time. If a project can actually take on a proper direction like this presentation suggests, that is a big selling point to me.

[1]: I know what the good things about choice are, I'm trying to make a point.

[2]: Widely regarded does not mean "universally regarded" or even "regarded as such by the majority".

[3]: Ignoring the problem that FreeBSD doesn't have the level of driver or application support that Linux has.
User-agent string changes
Maybe start a wiki page somewhere with what you know/want to know about Linux and then people can fill in the equivalent FreeBSD parts
Why JavaScript needs Types
Linux and OS X do the same thing to Windows (xbill, Micro$oft, PC vs Mac commercials, etc.) It is kind of sad, but it's how underdogs always work. Selling yourself as an underdog means not only pointing out what you do well, but how you do things better than others, and that always ruffles feathers.

Just saying what you do well will result in your competitors saying, "we do that well too", and won't win you any market share. You have to demonstrate that, "no, they really don't do that well." So it's a real balancing act between promoting yourself and not being a dick to your competitors. In my own personal case, I screwed that balance up royally, and it's a problem that has followed me around for the last decade.

Similarly, look how hostile OpenBSD is toward FreeBSD about security designs (watch any Theo de Raadt presentation.) I almost never see any FreeBSD users taking pot shots at OpenBSD like that. Then look at the market share of both, and it makes more sense.
Phase change systems like steam engines follow the Rankine cycle, which cannot reach as high an efficiency as systems like this which follow the Carnot cycle.
That's the entire point. Syslog has years of stability and reliability. You don't just throw that away, especially for such an important role.
I learned to send follow up emails to remind them I was waiting on their input. If I don't hear back in a reasonable amount of time it's an email.
Have you ever read some comment sections on Phoronix and /r/linux (or even LWN) when BSD is brought up? The lighthearted licensing jabs we see here are nothing compared to the vitriolic disinformation that is regularly seen when uninformed Linux users try to talk about other operating systems.

This is an infamous example: http://lwn.net/Articles/430598/ [gets particularly heated at mezcalero's top level comment]

Linux users make jokes at Windows' expense all the time. It's usually not higher profile developers doing it, but nor have they ever, really.
I don't think the predatory journals mentioned in the article are much of a problem for practicing researchers, since these journals are so far off the radar they may as well not exist.

I cannot imagine a serious researcher would even know the name of one of these journals, let alone ever consider submitting to them. The risk they pose is that non-experts mistake them for legitimate publications.
I don't recall seeing Facebook or Google have 15 years of uninterrupted service.
It's going to be hard to find an unbiased identification of the strengths and weaknesses of both. These kinds of things tend to bring out the definition of bias.

Anyway, I like the first comments idea about a wiki. That would be helpful.
It might help to know your main interest: bare metal server in a coloco? Virtualised servers? embedded? desktops?

Do you manage thousands/hundreds/a handful of machines?

Or is your interest entirely academic and structural?

I agree that most of the obvious Google searches return superficial comparisons of the installation process or explanations of the packaging and upgrade processes.
Can we stop making these responses every time anyone suggests a feature or critiques an open source project, please
Tutorial on Reactive Mongo with Scala, Akka and Websockets
Sherpas and Tibetans have thousands of years of natural selection to develop increased survival ability at altitude. Non-native residents of the mountain west states have only been there for no more than 167 years, having mostly immigrated from lower altitude regions.
List of predatory scholarly open-access publishers
> I just want to know about differences in design and unbiased identification of strengths and weaknesses.

There's no such thing as an unbiased identification of strengths and weaknesses, especially when it comes to monoliths like operating systems.

You say you're not interested in arguing about which system is better -- and I believe you -- but you're also asking for argument about which system is better, in list form. Heck, even your title has a versus in it.

That said, I join you in looking for a concise source of information about FreeBSD's design and usage in the wild contrasted with Linux.
only up to a point grad students at top end universities like Harvard and Cranfield will look down on those who could only get into the MBA
But ... why?

What does Material even offer to a Desktop OS?

And why a whole custom distribution, instead of a desktop environment?
WhatsApp encryption shows the value of metadata
At least in games Ruby has a hard time competing with LuaJIT; all that extra headroom is really nice to have, because 16ms isn't much at all.

Having said that, GC improvements are a good thing. Some of the RPG Maker folks will be delighted when this eventually reaches them.
Facebook Seeks Devs To Make Linux Network Stack As Good As FreeBSD's: http://bsd-beta.slashdot.org/story/14/08/06/1731218/facebook...

(I don't want to start a flamewar, just add more stuff for a good discussion)
To add some more details - being a good manager can be a delicate dance. When you are a manager, you start to become responsible for high level tasks that have huge impact to a company. However, if you micromanage too much, you create an awful culture of fear and hamper developer productivity.

So how do you inspire developers to execute in a timeframe dictated by others? You have to be a leader who inspires the engineers to complete the task, even if it requires putting in extra hours. This means setting the example, looking out for your engineers' welfare, being able to provide answers and not problems, and being someone who can be easily approached.

The moment something goes wrong, the burden is on the manager to make the right decision - the wrong decision can have negative ramifications over months, if not years. The moment you micromanage, something is broken in your process, or with the people involved.

I recently had to start wearing a technical lead & director hat - the intense pressure of the startup world bore down on my whole team in order to get a working product in order from scratch in about 1 1/2 months of coding. The resources became scarce since the technical lead got sick & had a family death, while two other senior engineers had babies in the time period. It then was left to two junior developers and me to do the lion's share of work until the other engineers could get back to work. I let the junior engineers work mostly normal hours (until close to our deadline) - I ended up taking the burden largely on myself, with mostly 75 hour weeks (even after the other engineers were back as well). During regular hours, I did some work, but was more focused on mentorship and any tasks that were blockers. The early and late hours were when I busted out complex code.

At the engineering level, good management shows as incredibly important, especially for startups. Pressure deadlines on engineers are taxing for all - good management by top level engineers is vital for preventing burnout in everyone else, which can make it easy for people to decide to leave a company, especially when compounded by salary that does not match what the free market has to offer.
Ask HN: Why memcached over Redis?
Our local celebrity tech company CEO recently said: "If you are a web developer and you use Redis for something where Memcached would do, I don't know what to say to you."

Hard to explain your reasons in 144 characters, and Googling gives me mixed information. Seems the consensus was they are about the same. So what are the nitty gritty details that put memcached over the top?
> 9. I found the disparity of income in the mountians of Utah very depressing.

Ironic comment from "marincounty". In my experience growing up in Utah, it seemed the wealthy people moving in all came from California.
But I can do that with jails. I can build a master jail and distribute launch a bunch of jails from it... or distribute it to other machines... extra easy if I use ZFS snapshots. Handle the distribution/deployment and maybe any extra configuration with your salt/ansible/whatever and you're fine.

What I see as a problem here for many people is that they don't want to do this all themselves and maybe docker offers conveniences out of the box. I get that. Someone needs to work on the jails tooling to make it more approachable so people aren't inventing the wheel.
I have to admit that I came to this thread to see if anyone accused Jordan Hubbard of not understanding the "Unix Way" when he mentioned that they need a subsystem like the one that must go unnamed on this and every other forum.

Gosh, I remember when you could get FreeBSD on floppies. I've always had a great deal of respect for the work that they do. 10.0 was awesome, but I have to admit that I don't use *NIX everyday anymore.
A lot of HN posts related to BSD release announcements end up with the inevitable "Can somebody explain the advantages of using xxxBSD?" comments. Might be worth looking at the comments section for some of those past submissions.
How App Publishers Can Leverage Cross Promotion Opportunities
16 Tips for Getting 90% of Your Work Done Before Lunch
You are right, I was interested exactly for the possibility that even the code that isn't particularly customized for the coprocessor would benefit from using all the cores. I always believed the GPU code doesn't do well with a lot of branches, and I hoped that Phi would better run such code than GPUs. Now searching, here's Nvidia's take:

http://www.nvidia.com/object/justthefacts.html
I am not certain that population density reaches its nadir in the Rockies. In those states (Utah and Colorado in particular), the population is clustered in towns and cities along the Wasatch and Rocky Mountain ranges. In the midwest there is a more rural distribution.

It would be interesting to look at suicide rates by population density at level lower than state or county.