skysight-inc/HackerNews huggingface dataset:
It was, historically, definitely a technical problem. You had to know what the base changelist for a branch was in order to integrate into it from trunk or to merge it back into trunk cleanly. I believe these problems may now have been fixed, but I haven't used svn in so long that I can't say for sure.

Regardless, branching and merging in git were designed to be straightforward from the outset. Due to the nature of git's commit graph it is straightforward to tell (with appropriate tools, and this is somewhere that git suffered initially but has improved dramatically as its popularity has waxed) where in history a branch was created and which commits are being merged.

If you want a branch and merge workflow where branches are used frequently and merges are the mechanism by which changes arrive in 'trunk' (which is basically how the Linux kernel is maintained with Linus being the final integrator -- he merges branches from what are effectively lieutenants who act as integrators for their respective subsystems) then git makes this workflow very straightforward.
What an incredible debacle. Select quotes regarding their technology decisions:

> "While SAP might be considered best in class, it’s an ornery, unforgiving beast. Sobeys introduced a version of SAP in 1996 and abandoned the effort by 2000. (It wasn’t until 2004 that the grocery chain tried again.) Similarly, Loblaws started moving to SAP in 2007 and projected three to five years to get it done. The implementation took two years longer than expected because of unreliable data in the system. Target was again seeking to do the impossible: It was going to set up and run SAP in roughly two years."

> "The company wasn’t doing it alone, however, and hired Accenture (which also worked on Loblaws’ integration) as the lead consultant on the project. [...] Accenture, which Target hired as a consultant on SAP, said in a statement: “Accenture completed a successful SAP implementation for Target in Canada. The project was reviewed independently and such review concluded that there is no Accenture connection with the issues you refer to.”"

> "The company had purchased a sophisticated forecasting and replenishment system made by a firm called JDA Software, but it wasn’t particularly useful at the outset, requiring years of historical data to actually provide meaningful sales forecasts."

> "The depots were hampered by other factors, caused by lingering data problems and the learning curve associated with the new systems. Manhattan, the company’s warehouse software, and SAP weren’t communicating properly."

> "The auto-replenishment system, which keeps track of what a store has in stock, wasn’t functioning properly, either. Like many other parts of retail, replenishment is an exacting science that can go haywire without correct data. At Target Canada, the technology relied on having the exact dimensions of every product and every shelf in order to calculate whether employees need to pull more products to fill an empty rack. Much of that data was still incorrect, and therefore the system couldn’t be relied upon to make accurate calculations."

> "To add even more headaches, the point-of-sale system was malfunctioning. The self-checkouts gave incorrect change. The cash terminals took unusually long to boot up and sometimes froze. Items wouldn’t scan, or the POS returned the incorrect price. Sometimes a transaction would appear to complete, and the customer would leave the store—but the payment never actually went through. The POS package was purchased from an Israeli company called Retalix, which worked closely with Target Canada to address the issues. Progress was maddeningly slow. In 2014, a Retalix team flew to Toronto to see first-hand what Target was dealing with. After touring a store, one of the Retalix executives remarked, “I don’t understand how you’re using this,” apparently baffled the retailer managed to keep going with so many bugs. But Target didn’t have time to find a new vendor and deploy another technology. [...] Unlike SAP, Retalix is not an industry standard, and why Target chose it isn’t entirely clear."

> "Like SAP, the replenishment software was brand new to Target, and the company didn’t fully understand how to use it."
The Atlas of Beauty: Universal Beauty of women across countries of the world
Imam Mustafa Efe lets stray cats into the mosque
Yes, I agree. The moral issue is allowing people to take out loans that they are unlikely to be able to repay, based on their personal finance history. I don't (yet) see how LendUp does a better job of that for first-time borrowers than any other payday loan company.

Perhaps this is addressed by limiting the first-time loan amount to something small (like $250), and scraping the borrower's online banking statements as part of the approval process in order to predict (based on the account history) whether they are likely to be able to repay within a month. I don't know.
My concern with the server side of this would be a bug in OpenSSL (which I assume this uses) could give a hacker access to the memory space of all current connections, a feature the default forking servers don't have to worry about. It's a benefit that helped qmail remain secure for so long.

And yet I say this as a creator of an async SMTP server, so I don't think these days it is that big of an issue.
Theres no list of either "upmods" or "downmods". Think about the frequency that feed would be updated.
NwAvGuy: The Audio Genius Who Vanished (2014)
Honestly, if you are working on a standalone feature with complicated math/distributed algorithm/transactional concurrency etc. only a handful people in the world understand, how is a code review going to help you beside trivial matters like code formatting/naming? How do you approach this situation in order not to upset the few people that can get it done?

I remember SUN's application servers had a licensed code inside their transactional core nobody was able to understand nor touch; it just worked as it was supposed to, prepared by a single genius who got it right.
You're saying that in reply to someone who clearly did, which seems disingenuous. I also read it the way the author intended.
> A small group of employees also made an alarming discovery that helped explain why certain items appeared to be in stock at headquarters but were actually missing from stores. Within the chain’s replenishment system was a feature that notified the distribution centres to ship more product when a store runs out. Some of the business analysts responsible for this function, however, were turning it off—purposely.

Business analysts (who were young and fresh out of school, remember) were judged based on the percentage of their products that were in stock at any given time, and a low percentage would result in a phone call from a vice-president demanding an explanation. But by flipping the auto-replenishment switch off, the system wouldn’t report an item as out of stock, so the analyst’s numbers would look good on paper. “They figured out how to game the system,” says a former employee. “They didn’t want to get in trouble and they didn’t really understand the implications.”

I think this article, and the employee quoted here, works too hard to excuse immoral behavior in their junior business analysts.
I disagree. The content and expression become constrained because a description of the problem domain has to be forced to fit inside them. Usually you can only make this happen with a drastically over-simplified model.

One of the tragedies of AI and CS is that it's easy to delude yourself that you've understood something because you can make a toy model of it - when in fact non-toy models that are comprehensive enough to be useful to a domain expert tend to be sprawling, irregular, complicated, and not very coherent.

The problem leads to a kind of paradox: Most human behaviour can't be simulated with an algorithm that's simple enough for humans to understand.

Violins turn out to be a good example. It's trivially easy to sample a violin sound. But sampling is nowhere close to being able to model the musical data bandwidth in a performance by a real string quartet.
While I agree a link to the file would be better, the frontend move towards npm and bower is due to greater professionalism in this area. It is fair easier to manage versions and automate installations by using npm and bower.
They use the English names in Japan. If you google for the Japanese official websites for these brands or even their products on rakuten.co.jp you'll see the brand names in English.
How many teams in the world have this problem?

My guess is not many. The 99% usecase in version control revolves around teams that need to enforce standards.
Well, for one, it would give your coworkers a chance to learn what's inside the black box, with you there to answer any questions.
Is pro-NSA a Republican stance?
Because liking the app does not necessarily mean it has the effect on sleep as claimed. I would be very interested in studies testing its efficacy.
I remember when this was first published, I watched the video and then rushed to install plan9port and try Acme. I used it for a couple of days before going back to Emacs, but Acme did leave a very positive impression on me.

- I really like how "unixy" of an editor it is; you can easily add new editing commands by writing a small program that reads from stdin and writes to stdout and use it to manipulate text within Acme. Of course, that program could be a shell script, a Python program or a Java program; Acme only cares that it can give and receive text.

- The editor has a mount point that contains the configuration of the editor and this can also be manipulated by external programs to influence the editor.

- The concept of addresses (e.g. an address into a file, an email address, a URL, etc.) and being able to click on such an address and have the editor DWIM is very powerful.

- I still don't know how to classify Acme: is it a minimal or a kitchen sink editor? You can make it do anything you want, but out of the box it is extremely bare. Is it a programmer's editor or a general purpose editing tool?

I'm not leaving my trusty Emacs, but I'm happy that I took some time to get to know something that was completely different.
> Furthermore it's mostly a rant against subversion rather than going making any kind of argument about his assertions.

A completely misguided rant at that. The author even admits it: "To be fair, you can adopt this workflow with Subversion, using either task branches or patches..." This is exactly how my team uses Subversion (and used CVS before it; yes, we used this exact "branch per issue, code review before merge" workflow with CVS up through 2013) and we don't find the overhead of branching and merging onerous. Granted, I haven't ever tried contributing to an open source project using SVN, but arguably Git is the more-correct tool for that kind of development anyways.
Silicon Valley’s $585B Problem
Note that the author's point about git (the technology) is what it enables users to do.

Teams can still use git or subversion or mercurial and have terrible code review processes, just as they can use Slack or IRC and have terrible communication, or use Ruby, C, Haskell, or ECMAScript 2 and have beautiful or nightmarish code.

Takeaways:

1) Technology is a tool, not an end in itself.
2) People are the hard part. Technology can open the door, but that doesn't mean someone will walk through it.
Android has adaptive brightness, which goes some way towards the goal.
Note that I did not exclude location and supply chain problems as part of their downfall, but I don't believe that their problems can be explained solely by those things.

Both Loblaws and the Brick had supply chain problems but they both recovered, mostly because they served the Canadian market.

Target, on the other hand, couldn't. Their marketing and in-store signage didn't resonate, their quality/price ratio was off, and their selection didn't meet the needs of most Canadians.
I don't write on paper anymore, but I still write all my comments first, then fill in the code.
The point of a framework is that you're supposed to build on top of it. Expectedly, color would be one of the first things anyone would change. Though the spacing issue itself might be difficult to address. Looking at the SASS files, _Color.sass has the values you'd need to modify in one place and _Spacing.sass might take care of the other issue.
There's no reason you can't do code reviews on SVN branches prior to merging to the trunk. My teams do this every day. It helps to have a dedicated code review tool such as Atlassian Crucible.

And I wouldn't necessarily characterize SVN branching as "clunky, user-unfriendly and error-prone". It might be slightly worse than Git, but with modern tools like Eclipse there's hardly a difference. I've never found SVN branching difficult at all.
Scheduler binding topologies go great lengths to mitigate this problem.

Don't over-subscribe the cores, disable hyperthreading, and bind scheduler threads to physical cores if your platform supports it.
> Plus anybody who advocates the use of git rebase --interactive as a sensible response to code review feedback is clearly insane.

Why? Prior to a series of changes being pulled into someone else's history you have all the incentive in the world to present the cleanest view of history possible. Moreover, if you can rebase -i on top of master you can turn the merge into a fast-forward rather than an actual merge. A more linear history with fewer merges is much easier to bisect as well as to read, generally.
The trick I was taught was to dry the light clothes (shirts, underwear, socks) separately from the heavy clothes (jeans, hoodies). Then hang the shirts up immediately after pulling them out of the dryer while they are still hot. Then you won't need to iron your shirts. It may not work really well for some dress shirts though.
My practice has usually been to ensure that the zero values of the types ARE a sane default for a struct if that struct is public and may be instantiated by a client. It sometimes involves flipping the semantics of some Boolean values around.

That, and judicious use of a New() function to construct and initialize types, help make up for the lack of default attributes in structs.
That's not what it's for, though. For graphics you need D6500, there's no way around it, circadian rhythm be damned. This is mostly for reading things late at night.
What's your workflow? Do developers check in bug fixes in trunk? TIA.
Yeah, why did they decide to stop at 40"?
Signalling theory absolutely does not indicate that.
For anyone who's interested, the github repo: https://github.com/trailsjs/trails
Never assume or generalize.

I thought that's what the title meant as well.
This is quite lovely. Very good job. :)

I for one would be very curious to read about how this works (too lazy to read code right now!)...
As you might have guessed, after a few conversations today (not very good ones, for the most part, I was tempted to give up the Internet.) I've been thinking about this code quite a bit in the last 12 hours.

I think you're right that there might be an opportunities for improvement. I admit that once the performance hit about 140 cycles per item, I mostly shrugged and called it a day. I felt a lot more concerned about its safety across various architectures than bringing that cycle count down to the absolute minimum. But I also did my benchmarking on x86_64, which has surprisingly strong memory guarantees by default, and so the difference here may be larger on other architectures.

Thanks for looking it over! I definitely am interested and hope to grab some time to try benchmark some tweaks (and test for correctness) on a bunch of different architectures.

Unfortunately I don't have all the state I'd need sitting at the top of my brain to revise this code at the moment, or even know whether your proposed changes are safe, since I find I can't write atomics code safely unless I devote at least an afternoon to the process of analyzing the problem's safety.

I remember there was a reason I chose using a shared item count instead of having the pointers be shared, I think mostly just to minimize the shared state to one thing, but it may not be the fastest choice.

If you want to give trying some changes a shot, I'd love to hear what you find! Email is in my profile. :)
That's not what that message says, but maybe you could email your auditors and ask if they'd stand by the assertion you're making that native apps aren't safer for cryptography than browser apps.

As for the rest of it: I'm sorry you feel that way, but I've reached a point in my message-boarding career where, after many, many years of fighting the good (then marginal then tedious then bad) fight, I'm just not going to litigate this issue anymore. What you're doing is now is a bad idea, and for the sake of your users I think you should port to a browser extension (and, eventually, to a native mobile app) as soon as you possibly can. Maybe you can improve your security before your popularity gets out of hand and avoid the fate Telegram seems to be falling into.

When new web standards make browser crypto viable, I'll acknowledge them. Unfortunately, the 10 years since 2005 have made browsers less hospitable to cryptography.
I'm pretty sure I got a 24% APR on my first credit card, $1000 limit. This was as a student with 0 history.

This seems like an INSANE spread.
"RPCEWGJ2 is a standard Executable ABAP Report available within your SAP system (depending on your version and release level)...If you would like to see the full code listing simply enter RPCEWGJ2 into the relevant SAP transaction such as SE38 or SE80"

Found some documentation on Google - I thought you were joking :(
What Causes the Smell of New and Old Books? Here's the Chemistry
Yeah, you're confused because I mis-wrote that. Wow, that was indeed a confusing sentence. I meant regs will hurt innovation, not security.

The problem is that I think the security gains will also be marginal, and the innovation harm will be significant.

In particular, the history of security standards, which you bring up as an example of "good regulation", is checkered.

I agree with you that mandatory insurance could be a "middle way" between intrusive regulation and no regulation. But that's essentially the structure the payments industry uses with PCI, and PCI has been a race-to-the-bottom.
You still can make dumb mistakes in genius code. And if your teammates can't follow the code at all, then it should either be better documented or they better educated. Having code that is untouchable because the lone genius left the company/got hit by a bus isn't something to be celebrated.
I think you just nailed why judging audio quality is so difficult. You can compare video frame by frame, or look at a still image for as long as you need to, but audio is always disappearing into the past as you listen to it, and the closest you'll get to freezing a moment in time is an annoying buzzing sound.
As I was reading, I started wondering how many other places in the US had this "across the road" setup. Then read "Plano" and realized "I guess for now, just the one!

That Walmart has taken a dive tho. I've rarely gone the last 4+ years, but it very much reminds me of the nearby one which is more "ghetto", just with different inside paint job (not industrial white).
Sorry I should have been clear about it. Yes. Part of the 5G Goal is sub 1ms latency. You will get most of the Latency improvement in 3GPP Rel 14.

So in real world, assuming the route between your Wired ISP and Mobile Network are the same, the latency difference on 5G should be less then 10ms max.
I have lived in SE Asia for half a decade and am currently in Taipei and honestly I see a lot of 15-30 year old Asians wearing Superdry. They invariably think it is actually Japanese. I haven't noticed older guys wearing it here but perhaps I haven't been looking.
I agree, I thought the argument was going to be against code reviewing branches, not for it.
How Much Does Your Commute Really Cost?
The leader of the British Labour Party, Jeremy Corbyn is a Euro-Skeptic

https://theconversation.com/with-or-without-eu-jeremy-corbyn...
I'm using acme for C/Go development for at least 8 months and I'm very satisfied. Acme is very stable and so much easy to extend using any language or simply shells. This turns the development a task much more painless.

In my current view, the lack of syntax highlighting is a great feature!

For now emacs is only for lisp/scheme languages.
> throw out the min and max and take the median of the remaining three numbers.

Do you really mean median here? Or did you intend to write mean?

If you're planning to take median, there no need to throw out the min & max first.
Arguably the newly supported guard syntax is nicer:

guard let foo = optFoo {
Swift.print("oops, this optional thing wasn't optional")
}

Swift.print("now \(foo) is in scope and non-nil")
You present a clean history, yes, but not a correct one. The context in which you made your changes, often noted as important, has been lost.
i did, seems a bit strange to me to be honest. do you use it? can you give some feedback?
This is great for comparing cotton or cotton blend shirts. I'd love to see the same data for shirts that don't use any cotton. We make fabrics for our own brand and usually stay away from cotton partly due to the problem of fit variance after wash.
Not him, but where I last worked once you had your dirty working directory, you'd run rbtool to upload the changes to reviewboard, where they could get looked at.

Once it was approved, you committed. A hook in the svn server would check that you had a link to the reviewboard entry, the entry was approved, and that your changes matched the diff that was approved.
You mean the (very plausible) allegation that NSA paid RSA to backdoor BSAFE, their commercial RSA library, by using Dual_EC as their default RNG. But that doesn't help your argument much either: the targets that used BSAFE were much more likely to be foreign and much less likely to be large-scale US communications infrastructure, virtually none of which uses BSAFE-encumbered software.

Just a reminder to other readers: RSA was originally the company formed in the 80s to commercialize the RSA algorithm IP. But in the mid-90s, a hardware token company called SDTI bought them and took over the RSA name. Tokens and enterprise multifactor auth have been the mainstay lines of business at RSA ever since, not crypto libraries.
This project has nothing to do w js, only css.
Yeah APRs are silly to apply here. Go rent a $300 TV for a week and then return it a day late and pay a $20 fee. If you wanted, you could call that a 2,500% APR.
Developers check in all changes (whether bug fixes or new features) on task branches first, and use those branches to run tests and conduct code reviews prior to merging to the trunk. That way the trunk build almost always works, and at any point in time we can deliver the trunk code to customers.
3 Day Blinds – Custom Blinds, Shades, Shutters, Curtains
Author here, happy to answer any questions.
Beware: wowmusix.com popup (just from clicking on the scrollbar)
Show HN: Coffee with me – founder.im
Futurist.
It interesting to see some passages tying the discovery with the faith in general. This is 1700s after all. And how the approach taken is in contrast to what a lot of fundamentalist or conservative Christians believe today. Talking about a deep resentment towards science and how they see it as an attack on their faith.

And it is funny that here is someone from 1700s, quoting an Orthodox Christian writer from more than 1500 years before who seems to be pretty ok with aliens living on Venus:

---

"St. Basil the Great considered the possibility of multiple worlds and said: "
As a potter, who made thousands of water pots with the same skill and exhausted no art and no power, the Creator of the universe has enough creative power not only for a single world, but
for as many as [He] wants to create in a single moment alone.
"

---