Same, and it's been for me like that for years. Even before Apple had their version of their keyboard, which I absolutely /love/. At some point it was very hard to find laptop-like keyboards for desktops. A lot of people laugh at me for it, thinking it's not a "proper" keyboard, but I think it just boils down to preference and I personally don't buy into the mechanical hype.
Really people didn't like XHTML because they didn't want to close their elements. That's it. And now most web pages don't even parse in an XML parser. What elements are standard and which are not is completely arbitrary, what the browser does with them doesn't really matter either. What matters is that you can extract the data from it, if you know the structure (either by following some standard, or by having out-of-band documentation). In that respect JSON and X(HT)ML are similar, except now you can't scrape web pages with a single GET request from the canonical URI, and instead need to run a fully fledged browser that parses javascript and/or read some site specific JSON docs (if any are provided at all).
Yep I was there. But XHTML did not die due to lack of semantics. One of the things it had was namespaces, and people did embed other XML specs in their documents (remember MathML, RDFa?). It was just too complicated for most people, and when AJAX became a hit people flocked to JSON. Remember, AJAX used to stand for Asynchronous Javascript and XML(!) that part got lost in translation somewhere. Besides, with JSON all the semantics are out of band in some (hopefully well written) doc, rather than in a schema or DTD (which used to resolve in band, even). Comparing JSON to HTML in terms of semantics is silly: both have none. But the idea of using hypertext markup for both display and machine readability, that's something that I would still like to see resurrected
Now I don't want to be a downer: but we collectively seem to have forgotten that HTML as a markup language with sufficient semantic elements, is a perfect API in itself. In fact, if we had stuck with XHTML I would've postulated that it would've been an even better API than JSON due to XPath, XQuery and XSLT.
"HyperText is a way to link and access information of various kinds as a web of nodes in which the user can browse at will. Potentially, HyperText provides a single user-interface to many large classes of stored information such as reports, notes, data-bases, computer documentation and on-line systems help. We propose the implementation of a simple scheme to incorporate several different servers of machine-stored information already available at CERN, including an analysis of the requirements for information access needs by experiments… A program which provides access to the hypertext world we call a browser — T. Berners-Lee, R. Cailliau, 12 November 1990, CERN "
Web apps are somewhat backwards in my opinion. We completely lost the idea of a markup language and decided “wait, we need an API”. So we started using JSON instead of the actual document (HTML or XML) to represent the endpoints. And then we patted ourselves on the back claiming “accessibility".
And here I'm sitting with my 8" Schmidt Camera and 12" Newton … the amount of engineering that goes into this is incredible. It's not just the mirror, which is of course important, but also having a mount that can precisely track at the sidereal rate with all the mirrors on it. And then, judging by the image, they'll also do Laser Adaptive Optics to correct for atmospheric seeing artifacts, which means adjusting the mirrors and/or camera at a very high rate and /very/ precisely. It basically works by painting and artificial star in the sky with a high powered laser, and by measuring the difference between where it should be and where it actually is, you can then adjust the optical train to compensate. And, then there's the issue with temperature compensation, collimation (looks like a Gregorian-type design), and of course the cameras themselves. For the cameras I'm assuming the illuminated field is quite large, so either this means a HUGE CCD, or stapling several together with all sorts of noise artifacts involved. Very exciting. Very hard.
Absolutely, always wanted to finish my Epidemiology PhD. But eeh the pay is awful. Not that I /really/ care, but that's getting into personal details. Still, whatever I could come up with now would not be much different than what I would come up with during academic research. The machine in my head is working regardless.
Exactly, and that uncovers the folly in this: what are you trying to do. Often enough it's very specific, and requires actually going out into the world. Sometimes the literature is already there. But nearly always it requires some form of analytical thought. "I want X because I need to prove Y". There is no AI magic sauce around that. It means that the people interacting with the "user friendly" interface need to know, and need to know how to get there somehow. That's rarely the case. And from a product perspective it makes things very hard: you get bombarded with very specific requests that require time and effort to build UIs and models for, that at the end the of the day only solve that specific question. Instead, it would be better to equip people with the tools needed to solve the meta-question so to speak, but that meta question is much much harder (at least, I've been trying but no success yet). As a funny anecdote: my medical knowledge had exploded. But I see that as a symptom of the broader problem: I know how to do /some/ things because I've gained that domain knowledge, but I can't teach the system yet to solve the "general" problem because a) I don't know what it is b) there is no data to get there c) what even is the UI for that.
yep, we're trying to outcompete them. But it's a hard thing. MetaMap: we beat it, cTakes, we can do it faster. But really how many < 80ms concept recognition systems do you need that work on 28M documents. And if you have that: what are you going to do with it. We have, internally, systems that predict dense vectors based on CUI graphs of concepts in text. Great for similarity search: but utterly useless in the end.
1) As someone who does NLP and AI for Evidence Based medicine [1] I can only agree. I build natural language processing tools, together with the team, for EBM. I have /no/ idea what to do next. Please. Help me.
2) Rant: here's the thing, we have SVMs, LSTM, BiLSTM-CRF, Knowledge Graphs, 28M articles, deploy infrastructure, tests, you know all the cool stuff. We can't sell it. It's PubMed this, PubMed that. There's no breaking that spell. So instead of building a better search engine, we focused on better analytics. Is it cool, sure. Is it as good as all the KoL stuff from LexusNexis, nope. Medicine is /hard/, if you think your app is hard: medicine is /harder/. Am I trying to cover my ass, sure. But seriously, deal with everything being non-standard and proprietary for long enough and you'll feel the same way. 80% of my job is saying "no" to people who aren't going to pay in the first place (Sanofi, Novartis, etc). They don't care. I'm just going to ride this out, throw some blockchain in somewhere where it makes absolutely 0% sense, call it a day. Seriously, NLP/AI for medicine: it's crap 100%.
And, I'm a "senior developer" with publications behind my ass on this. I don't know what to do instead of riding the hype train. Seriously: anyone out there that knows what to do with 100M+ medical publications in a 100M+ knowledge graph, be my guest: I'd hire you in a heart beat. But it's hard and there is nothing to be gained AFAIK.
Even for a simple amateur astrophotographer [1] the SDSS data is invaluable. It powers most of the target selection, and provides accurate coordinates for most astronomical objects. Combined with Plate Solving, it makes my life much easier [2]. Take for example a well known tool "Sequence Generator Pro", I only have to type in a name and I can start imaging [3]. I can't thank the people enough who worked on this. I'm soon upgrading the telescope with a set of Sloan photometric filters (used in the survey) [4], and particularly interested in expanding my images with Near Infrared data. Which can also give very pretty pictures [5]
I've had high blood pressure since 24. I've had every possible diagnostic test, tried medication (no avail). I'm not overweight and do walk about 50 minutes a day, eat as healthy as can be expected. And still it averages around 170/90. I gave up on it. If global disaster doesn't kill me first, it'll probably be a heart attack around 50. There are worse ways to go. Seriously, even lifestyle changes for the relatively healthy only seem to make a 10 mmHg difference, so eh. Whatever.
Haven't tried in years, so it might be better now. But, last time I tried it was more of a hassle and frustrating than setting up Hackintosh. Trade-offs, I guess.
Having ran Hackintosh for 6 years as my primary development workstation, I have to disagree. All the points are true, and it's been very frustrating. However, to me OS X is the only really viable OS at the moment (Unix base that runs mainstream software well like Adobe and MS Office), and I'd rather run that on a machine that I know, can upgrade, repair and take apart if needed. And Hackingtosh is that, and if it runs, it runs smoothly. 6 years of 32GB memory, quad core Xeon, GTX 770, 34" ultra-wide, and plenty of native IO and storage ... try beating that at the price point of a Mac Pro or iMac. But maybe 2018 will be finally the year I drop OS X altogether and use Linux on a laptop and my workstation. OS X is slipping, and the hardware is not what I need from PCs anyway. Windows is still a no go, though.
Eeh I have quite a few of these in data centers for Deep Learning work. What am I supposed to do now. Swap them out for Tesla/Quadro cards? Switch to AMD or Xeon Phi? Or just ignore it and possibly violate ToS. Nice move Nvidia ...
Maybe it’s different in Europe. But I’ve had nothing but bad experiences with AppleCare. Except maybe for that time where they replaced a charger free of charge that literally caught fire.
AppleCare covers almost nothing. Any cosmetic thing they can find "out of warranty". And 3 years is not a lot for a machine that can cost up to $10k. Besides, they erase your data and it often takes weeks to fix (or even 1,5 months in case of my Macbook). They require you to give up your password (a nuisance to say the least if it doesn't boot at all to change it). And besides, there are a lot of places on earth where there is no certified Apple Dealer without a substantial drive or even flight. It just bugs me that a consumer electronic vendors have aggressively started implementing a model where it's no longer /your/ machine. You rent it, and with the flick of a switch they can brick it or decide to no longer support it. This icks me particularly because it's labeled a "Pro" machine.
Or repairability. And, before anyone mentions that it's impossible to fix SMD, it's totally doable.
Just as an example, https://www.youtube.com/user/rossmanngroup click any of the board level repair videos.
(and I mean, this is HackerNews, the ability to tinker with stuff or keep a historical/cultural legacy of these things for decades is pretty ingrained in the general "computer crowd").
I just find this user hostile to be honest, they would probably lose 0 customers over publishing board schematics and making the back pop off. Now in a few years, all you have is a pile of steaming metal, with no hope of ever repairing it (for any reasonable price) after Apple decides they're done with it. It's planned obsolescence for a market that should know better: pro's. I would think twice about rolling this out in an enterprise setting or any critical piece of infrastructure. It's a toy, an expensive one at that.
It's definitely possible. https://www.youtube.com/channel/UCl2mFZoRqjw_ELax4Yisf6w (he does a bunch of different issues, just click any of the board level repair videos). I mean if you don't own the equipment yourself (or don't feel like doing it) I don't see why /other people/ well versed in doing it should not be allowed to. As a so called "pro" AppleCare is not always an option. You loose all your data and often enough have to wait several weeks to get your device back...and in a lot of places there are no certified apple dealers in a 700 mile radius. It's just user hostile, and completely unnecessary.
Or do any sort of repair on the thing. It's quite feasible to do basic board level repair with the schematics. But not without the schematics or if the thing is welded shut. It's wasteful, and I sincerely hope one day we can have a proper "right to repair" act. I mean, this has nothing to do with user experience, security, or aesthetics. It's basically just an anti-consumer move on Apples' part. And, I honestly don't get why. What are they trying to protect? Just put some screws or other mechanism for detaching the thing and publish the board schematics. They won't loose money over it.
Yep, and it's so slow. On my new desktop rig (2017, $3,5k worth of hardware) it's ridiculously slow. Opening a exporer, wait 2 seconds. Open a network drive, it might open, if you're lucky. Even mundane things like opening Adobe software or Office takes noticeably longer than on my 2014 Macbook Pro. And it's not the hardware, geekbench is in expected territory, AIDA64 benches fine. It's just somehow, slow. Feels slow, at least. And then there's the visual inconsistencies. Open the details on a network view and EVERY TAB has a different UI style (one of them going back to the early 2000's) I find that inexcusable. But hey, games, they run fine.
The really cool application of this, which they allude to at the end of the paper, is multi dimensional indexes. For example right now kNN for similarity search (think recommender systems) is usually done with some form of K-D tree or projection method. This has a bunch of downsides, including memory usage. If we can "learn" that index directly, that would be really fancy.
Good point. Force of habit. Unfortunately I can no longer try since I set the root password under the Directory Utility, which probably changed the state of the system.
Apparently someone verified that it /does/ also work with `su - root`.
wat. confirmed on 10.13.1 (17B48). I was even able to add another super user.
Edit: changing the login method to "Name and password" under login options, then logout and login with "root" with empty password also works.
Fortunately, it doesn't work on cold boot with FileVault enabled, at least it doesn't appear so. `sudo su root` also doesn't work with an empty password.
I'm not an economist. But here is my arm-chair philosophizing about what is happening. To combat the economic crisis we started printing a lot of money. This had two effects: the interest on savings went way down, and the loans became very cheap. Having money = bad, having debts = good, at least for those who can carry the burden. This was done in order to incentivize investing, thus growing the economy. Obviously, that worked: property price and valuations went way up. But those are driven by the future-promise of debt repayment. The moment we stop printing the money, people will get wise and try to sell off those assets again. Because then having money is cheaper than having debt. So now there's a bit of problem: we can't keep printing money faster than the economy grows due to hyperinflation, but we can't /really/ stop doing so either because people will sell off their debts in order to cash in on cheap investments. This to me, seems problematic.
Here's something odd I noticed. The previous crisis obviously had a lot of detrimental effects. However, it also made some people /very/ rich. Basically if you invested smartly right after, you would have more than recovered the losses by now. I think people are anticipating that, I know I certainly am. Next crisis, hopefully sell before it happens and then buy for longs. I'm not quite sure if that /anticipation/ was just as ingrained before. Maybe I've just gotten older and notice it more, maybe it's a real thing. But whatever it is, it's quite dangerous, because it's a catalyst: if people want it, it will happen faster than before. Couple that with real externalities (geo-political tensions, climate change, resource depletion, overpopulation) we might be in for a dangerous disconnect between market movement and "looking out of the window".