skysight-inc/HackerNews huggingface dataset:
Are you really restricting the pool though? Most devs can't write or efficiently develop a GC. Learning a language is easy compared to writing a reasonably performant and correct GC. Anyone in this area worth their salt can pick up C if they don't know it already and, again, they probably already do if they have experience at this level.

I've been hearing 'C is dead' for fifteen years now, but it hasn't gone anywhere.
It's not going anywhere
That's not what Washington thought:

> ....you have the same religion, manners, habits, and political principles...
Wanted to say that, in addition to agreeing with what you wrote here, I've noticed myself frequently nodding in agreement with your other nicely worded and considered comments.

I prefer your version, but I would like to share a slightly different formulation of that aphorism that is equally amusing: never argue with idiots, they'll bring you down to their level and then beat you with experience.
Too bad the author doesn't show specific examples. I can sympathize with the sentiment. The problem with scaling languages like python and ruby in my experience is the number of moving parts and jump in deep knowledge required to scale when your application takes off. One day you're happily writing compact code in your favorite language and suddenly you're rewriting core parts in C/Go/Rust while learning a new language and bolting on a variety of moving parts like redis, memcached, etc. to keep your business from becoming a victim of its own success.

A lot of the problems are more or less solved problems with well known workarounds but it's still a pain and probably why there's so much buzz around finding the "next (insert your favorite language/framework)".

Erlang generated a lot of buzz several years ago but aside from the recent success of WhatsApp it never quite stuck. I'm curious to know how this author thinks differently.
They run lots of programs and see if they crash/leak.

(Seriously, Go is not really an academic language caring for that kind of stuff, unless it comes off easily to prove it).
Lawyer Wins Red-Light Camera Lawsuit Against Richardson
When I was writing trading systems on JVMs we were much more worried about allocation costs and memory access patterns than we were about GC. The former issues impact the normal latency while the latter impacted the worst case. Now you needed to think about and deal with the worst case, but as you say, making a system that doesn't GC often is pretty straight forward.

Now that I'm writing high throughput systems in go I use many of the same techniques that I did writing low latency systems on the JVM (arena allocation, memory locality, etc). This is because the other 2 parts of memory management, allocation and access, continue to be major drivers of performance even though the deallocation step is fundamentally different.

That is to say, GC times are not the only thing that matters when it comes to memory management and it is a relatively straightforward tradeoff between deallocation and allocation that the current golang GC is making.
Sounds interesting, but 404!
How Hardware-as-a-Service will save IoT
I'm always surprised why more people don't just do F12, ctrl+shift+M (on Chrome) while writing their websites. Just four keystrokes :)
The lesson learned over and over in the West, is that any add-hock development of the spectrum results in huge future inefficiencies with large blocks of spectrum locked out of re-use due to poor planning in the early days.

The temptation is to let companies use new frequencies wherever they want, but in the longer term this results in chaos, and the only solution is to rip it all up and start again (at huge cost and disruption to service).

The only workable approach is to design an interlocking network of spacial and frequency allocations and then stick with it, and make sure that each block is fully utilised before moving on to a new block.

With all of the above considerations, the cost of the actual network hardware is negligible, especially if the consequence is that poor villages will have to abandon their total investment in equipment at some arbitrary point in the future.
One point for you!
I think you misunderstood my comment. I was not saying that mysticism is correct, but that there are matters that are beyond the understanding of the human mind, including natural science.

As to natural science being the only road to truth, natural science is itself founded on human experience, and human experience is also the basis forms of truth, such as ethical and mathematical.
Even if Luakit itself is getting commits, last I checked the underlying webkit code it's based on doesn't get security updates, so as much as I would like to use it; it's really not a good idea: https://blogs.gnome.org/mcatanzaro/2016/02/01/on-webkit-secu...
Well, in our group we just started (academic) research testing out possibilities to bring data analysis, visualization and remote collaboration to VR (Vive).

I'm quite curious whether this will work out and what the future will hold for us.
News for Normal People
If you pinch and zoom on any touchscreen device I've ever used, you zoom into a section of the page, not the text. That is, you end up having to drag left and right to read a full line of text, which is not ok.

That said, I find the font size on mobile fine. On desktop I always have to zoom the text 3-5 ticks.
Check out Virtual Desktop
MSX2+ Emulator right in the browser. My '90s are back again
Good hand tracking is a total game-changer though. I suppose you could wait for Oculus Touch.
My understand is that Black Sea states do not have a tonnage limit, which is how they get around it.

If France loaded some anti-ship missiles on the Charles de Gaulle carrier, it could be called a missile cruiser (with planes) but would violate the tonnage limit (its about 50% heavier than the tonnage limit of the treaty).

The treaty is doing what it was designed to do, I think, by limiting non-Black Sea ships through the strait.
"China's economy a debt bubble in disguise" <-- There, fixed it for you.
One thing that is very helpful is that you can navigate the code in your editor using the exceptionally effective code navigation tool for Go. With the tool one can very easily and precisely jump to the definitions and references without building an index beforehand.
Wow! Graphics and sound are very nice in this one.
Will try to connect with my retro joysticks back at home!
I'm really curious if this is based on your actual experience with a Vive or if this is an assumption based on what you know about the technology.

I read an article at some point that claimed this was an issue so I consciously tested it in the unit - focusing on something near my face and then farther away without moving my head and it actually feels (to me) pretty correct.

I don't really know the science behind this versus light field displays or whatever, but if you have access to a unit I encourage you to try it - it's very difficult to detect issues with focus and it absolutely does not look flat (again, to me).

I would be very interested of all the opinions in this thread which of them are from people who own a unit and have tried these things and which are assumptions.

This technology is so incredibly convincing I'm embarrassed to say that I fell over trying to lean on a virtual pool table at one point. I simply forgot that it wasn't a real thing. :)
Swift is more high-level. That's not an accident: Swift is designed to write the front end of an interactive application, while Rust is designed to build the back end thereof. But if you're coming from dynamic languages, Rust's biggest talking-point advantage over Swift is how easy it is to integrate Rust with other systems.

Rust doesn't have "special integration" like Swift does with Cocoa, but it will talk to anything that will talk to C. Which is basically everything. It will talk to Java's JNI (including Android NDK), it will talk to Ruby's MRI, it will talk to CPython, it will talk to Node, and I can even integrate Rust with Swift. [It's pretty much just a matter of converting the function declarations and asking to have your project compiled into a C shared library.](https://doc.rust-lang.org/book/ffi.html) ("rust-bindgen" and "rust-cheddar" automate this)
One of these innovation centers popped up recently next to our office. These are basically re-purposed "ghost malls" for malls that couldn't make it in retail, of which there are many. So call it "fall out" from the real estate bubble more than anything, and who wants to be stuck in a window-less subterranean labyrinth? Not the best place to be innovative.

At least this is in Beijing Zhongguancun, which does have a startup scene...kind of. And such space might be appealing to lower cost startups who don't want to rent office space out in the suburbs.
playing Aleste2 with my wireless XBox360 joys right now
I loved Pascal instantly because my first language was mainframe APL, followed by some weird in-house macroassembler that Xerox was using on its 8080-based business boxes. Compared to APL, Pascal is not only elegant but transcendent. Verbosity bothers me not at all (I used to write COBOL too) because I like being able to read and understand what I've written six months after I set it aside. You couldn't do that with APL, and I had a lot of trouble doing it with C.

As a few other people here mentioned, I'm creating a FreePascal edition of my ancient Turbo Pascal book, ripping out stuff that nobody needs anymore, like CGA graphics and TurboVision. (I believe that there's a Turbo Vision clone available for FreePascal, but I just can't force myself to learn it again and write about it, even though I was writing paying apps with it in 1993.) The book is free, and the current version (I tinker with it irregularly) can be found here:

http://www.copperwood.com/pub/FreePascalSquareOne--08-06-201...

I'm going to stop building the release date into the filename with the next release; just search for "FreePascal SquareOne.pdf".

I'm programming almost exclusively in Lazarus these days, a lot of it for the Raspberry Pi. At some point I'd like to write a couple of shortish books on specific Lazarus topics like databases, and once we get settled in Phoenix I'll give it a try.

BTW, my friend erbo told me about this thread, so I figured I'd stop in and say hi.

--73--

Jeff Duntemann K7JPD
Can I ask why? Do you not feel like the medium of VR gives you presence and adds something that no other medium does? To me I'm more concerned about the content and if that can be 'solved'. Also if there's no way to fix motion sickness with standard "non-neural stimulation" technology then it will always be limited I think.
I don't know how much of an advancement this is for a seasoned user, but I do think this would be a great learning tool since you can visually see all the commands generated by the terminal.

That's what shines in my eyes from this project.
Metaballs and WebGL
I'd argue that one of the biggest differences between golang and java is not technical but cultural. That is, the golang idioms and thus the std libs are quicker to reach for things like object pools and other performance "hacks". Even the std http library uses an arena in golang.

Similarly, high performance Java libraries like the Disruptor, SBE or Chronicle look very much like C code.

Personally, that doesn't bother me, as it allows you to write your hot path and your non-optimized path in the same language with the same tooling.

says the guy who has split JVMs across processes for performance and contemplated doing it per core
>> Was shocked to see that your durability (27 9s) was so much higher than what S3 claims (11 9s)

> 27 9s is literally higher than my confidence that human civilization will be here in the next second. 10^27 seconds is about 32 quintillion years. Extinction events occur with a much higher frequency than that.

Without reading the article, I'm assuming this is the uptime probability they promise - so ( 1.0/10^9 ) * 365.25 * 24 * 3600 * 300 ~ 1 second of unavailability every 30 years (AFAIK Amazon is pretty far in the "red" on this one - they've had a few outages?) [ed: initially was off by a factor of 100 (and 10 in error...), the two 9s before the comma - the "compliment" (1 - p) of 11 9s is 1/10^9, not 1/10^11)].

11 9s is already effectively the same as will "never go down in a way customers will notice" (actually a second every 30 years per region isn't entirely insignificant, only almost insignificant). A higher guarantee does indeed seem silly. It's probably much more likely that we'll see annihilation by global thermonuclear war (for example). In which case I'm guessing the data would go off line for a while -- so such a number is meaningless.
It's not even that the paragraphs are long; it just a crazy scattershot of every conceivable combination of quote blocks, italics, bold, dot points etc.

It's like they wrote the piece as a Markdown example to show someone how you can format text any way you can possible think of!
Ask HN: What are your startup ideas that you aren't pursuing?
I'm not clearly understanding what
you wrote:

What about "focus"? User's
focus when the look at the
screen; my focus when
I have to work on all the issues
in the startup and, then, in
addition the ads and, thus, lose
my focus; something else?

For user experience, with
my Web pages, the ads are fairly
easy to ignore. The pages are dirt
simple with essentially no JavaScript --
so that pages don't jump around.
And all the layout is just via
tables so that I know to the last
pixel where everything is.

The content the user wants
is on the left, and some ads
300 x 250 pixels are on the right.
Simple.

So, I'm guessing that the
ads will not be very distracting, e.g.,
won't hurt the ability of the
users to focus on the content,
i.e., won't yield a poor user
experience.
Awesome! Is there a way I can make this the default?
It's a paid terminal emulator, written (by all appearances) in some kind of Electron-like (so a much much higher footprint), with a GUI for what can already be done via aliases, functions, and scripts.

And no telling how well $TERM detection works (show me vim! Show me something that wants 256 colors!)

If it was free, I might still not use it, because my terminal emulator needs to be lightweight and bulletproof, not heavy and shiny. A terminal emulator is a hammer -- simple, solid, good for constant use -- not an art piece.
I understand that, and as a developer, I'm used to working with stuff like this.

However, without some sort of interactive IDE, this just feels like magic numbers. The code itself, as written, is not enough to help you visualize what you are producing.
A new medium never really replaces an old medium, it just starves all other media for time.

Really? So, TV and movies starved audio commentary and discussion for time? I suspect TV and movies became dominant, but they didn't completely eliminate audio. Games are a new medium, and they seem to coexist with other media. Books don't seem to be going away. If anything, new forms of media seem to be synergistic with the existing forms.
Gross negligence AND the actual loss/spillage of the information would, together, be sufficient under section f. Is there evidence of the latter?
Great application.

Will also replace pictures in real estate listings I suppose.
Doctors give an oath [1] to help all sick people.

Public park designers, and even municipal clerks who actually order benches and suchlike, do not do anything similar.

[1]: https://en.wikipedia.org/wiki/Hippocratic_Oath
>We may have passed "peak social".

The latest megainvestment cycle was largely inspired by facebook (and enabled by zero interest rates).

It's interesting what happens to Facebook. The founders all cashed out. But the main product is dead. Will Instagram/WhatsApp maintain its market cap, or will it implode? Will it buy Snapchat and continue to buying anything new that is fashionable? I am actually curious about the opinions here.
It's naive to assume there are no trillionaires currently.

You really think the Forbes richest list represents the actual richest people on earth?

If you have a bit of time to kill google 'Spiritual Wonder Boy'.
Why is Big Ben falling silent?
What’s the point of the PhD thesis?
Things will change when Oculus Touch comes out. I don't understand why people are already dismissing the Rift as if it's the final revision, especially in such an immature market such as VR.

Oculus is still more focused on non-roomscale experiences for now, but they're already starting to change how they talk about it, no doubt in preparation for Touch. The tech is there, the games are there (from Vive-land), the only thing really missing right now are the controllers.
Interesting concept, but I'm not sure who this is directed towards. I can see some people using this, but not that much. (experienced) Developers will naturally go towards the features that shells like bash/zsh offer (e.g. aliases), and most inexperienced developers... well, I don't see them putting that much effort into configuring their terminal, and besides this, most people in the Linux world will hardly pay for something that they can get for free from somewhere else, unless it really is a necessity, which doesn't seem to be the case here. That said, I wish you the best on that. Always good to see different stuff.
> Writing "if" statements without short-circuit operators is both tedious and error-prone.

By default both Delphi and Free Pascal perform short-circuit evaluation of boolean operators. The Delphi and Free Pascal documentation has more:

http://docwiki.embarcadero.com/RADStudio/Berlin/en/Boolean_s...

http://docwiki.embarcadero.com/RADStudio/Berlin/en/Expressio...

http://www.freepascal.org/docs-html/current/ref/refsu48.html...
There have been similar Smalltalk-in-Smalltalk, Lisp-in-Lisp, and Java-in-Java, etc. projects.

I have yet to see one that lead to better garbage collection.
I've been programming Go for almost 2 years and I routinely get stuck trying to figure out the "right" way to do something in the language.

For reference, I felt comfortable in Java, Scala, C# and Perl all faster than Go.
From their MICRO'15 paper (section 5): "We use an in-house microarchitectural, event-driven, sequential simulator based on Pin".

This is fairly standard for computer architecture research in academia: the results are based on a cycle-accurate model that simulates what the machine would do when running particular code. The field has a standard set of benchmarks (e.g. SPEC CPU2006 for serial code, and a bunch of different ones for parallel code) that are run on these simulators and are well-understood. The same is true for architecture teams in industry: they start with simulators and (a lot of) benchmarks before any silicon ever exists.

The reason for all of that is that actually fabbing a chip is prohibitively expensive and insanely work-intensive. A real chip has probably millions of lines of Verilog RTL, and a lot of custom layout to get anything reasonably performant (then > $1M for a mask set, multiple weeks or months to get the chips back from the fab, etc). In contrast, a good simulation model, worthy of publishable results, of an SoC with out-of-order cores, a cache hierarchy, and DRAM, is somewhere between 10K and 100K LoC of C++; the model for a new proposed feature is maybe a few KLoC of code on top of that. Once the simulator exists, a grad student can try out new features fairly easily. It's also much more analyzable and instrumentable: a chip is mostly a black box, modulo whatever debugging features you build in, while a simulator can easily dump a "pipe trace" of the pipeline state every cycle. The field has invented lots of different tools and ways of visualizing data to get a sense of what goes on inside the machine and what bottlenecks exist.

So basically, it's a software model, and the software model is much more informative, and easier to tweak and iterate on, than silicon while being "good enough" for trustworthy results.
Just FYI, the "Bro" in the logo looks a lot more like "Bra" to me.
You don't need to be, but if you can't read C, I'm not sure how much extra value you are going to get from reading how a particular garbage collector works.
If you're like me, you'll think, "aliases!"

But, the shell is a bunch of nontrivial things to learn. Tools like Go Terminal_ could make a less discontinuous learning path for shell. I recently had to teach[0] someone a bit of shell, and I kept tripping over explanations of:

command -[flags] arg1 arg2 arg3 | something else

Merely explaining that -xvf modified tar and how was a challenge. After I explained it, the user appended -xvf to cat in a different session. The above line would be a dozen lines of code in a blub. Shell takes a long time to grok.

All that said, I wouldn't call Go Terminal_ "efficient" ;).

[0] I did a terrible job.
One of the myths is that spectrum "in the middle of nowhere" is unused.

Most third world countries have enthusiastically adoped mobile phones and have leap-frogged the creation of landline networks.

The result of this is two-fold: The Radio Spectrum is heavily used, and also very inefficiently used as so much traffic which should be carried by landlines is forced onto mobile networks.

If you've traveled in remote areas of Thailand, Cambodia or even Laos, you'll be aware of the incredible penetration of mobile phones and even the Internet.
Huh, I turned off web search tracking years and years ago. Glad to see they (apparently) honored that and the only thing that was being tracked was the random youtube visit.
Check out Dediserve - https://dediserve.com. They let you customise the resources (including SSD and NAS storage) as per your needs. Moreover, their performance and support are great too.
I might not see a developer using this, but an administrator I could. Needing to run one-off scripts and server management. However only if it would work remotely, and with host specific configuration and command options.
A middle-out compression solution. Decided to make video chat software instead.
How about an arcology overhaul route?

Make more of the 'common' inner areas a combination of hydroponics (above) and greenway parks (beneath). Use skylights and/or artificial sun-lamps as necessary/effective.
Sculapio
لطفا بیشترتو ضيح بدید ? I tried Google for translation. It wasn't very helpful.

Edit: ok, close enough --

"Please explain me Byshtrtv"

Edit2: replier and op were much more helpful than google, thank you!
So has our lab! We should really share some knowledge and experiences. If you ever need another academic lab in London to try some stuff out then give us a shout.
In my (limited) experience, treating your CI pipeline like a distributed system is a design smell. It leads to build processes that are difficult to test, fix, and iterate on.

When a build system can only be effectively invoked by CI/CD, it starts to pervert developer incentives. People need to check things in before they can be sure they work. They don't bother with tiny fixes because of the inertia. Flaky jobs get a quick rebuild, because reproducing a build failure locally is complex enough that they'd prefer to avoid it if they can.

Over time, these add up to a system that grows through accretion, which is the enemy of both agility and understandability.

Better is a build process that uses simple, reusable components that work equally well on developers' machines. These tools can be tested, refined, and replaced incrementally, using the same build processes that the rest of your code base does. You can do this without needing coupling your build processes to the specific way(s) that Jenkins (and company) model builds or their configuration.