Live data from Hacker News

Autocomplete from Stack Overflow

emilschutte.com

111–120 of 151 posts

Re: Autocomplete from Stack Overflow

#111

Earlier quoted context omitted.

Or just not support older IEs. http://browserupdate.org/

Maybe the likes of you someday will get a job and then understand that "what you support" does not depend on you.

What I do, is provide nwjs to those on old versions, so they think they are getting the "application" version, but in reality, its Chromium hard coded to only goto the web application.

So far its a win for both parties, since they are not installing another browser than can interfere with some silly IE6 only internal enterprise site and we get to use the latest browser features.

Re: Autocomplete from Stack Overflow

#115
post #62

It still astounds me that we haven't solved reusable modules in 2016. Sure, we have libraries, apis, package managers etc. but every time I read a code base, there is always a utility function reinventing the wheel. Someone wrote it because it is still difficult to discover modular code and reuse it easily. It's pretty nuts when you think about it. Imagine mechanical engineers having to recreate the same CAD file bec…

True. Stuff like common functionality (regex engine, math functions, talk to postgres, etc) should be written once, and consumed with higher level interfaces from all other languages.

The problem is we don't have a safe, easy to build and package with everything else, and easy to consume (without performance penalty) language. The best we have is C, which is not enough.

Re: Autocomplete from Stack Overflow

#116
post #93
post #62

It still astounds me that we haven't solved reusable modules in 2016. Sure, we have libraries, apis, package managers etc. but every time I read a code base, there is always a utility function reinventing the wheel. Someone wrote it because it is still difficult to discover modular code and reuse it easily. It's pretty nuts when you think about it. Imagine mechanical engineers having to recreate the same CAD file bec…

We've come a lot farther than you may realize. We've come far enough that, having removed a lot of the accidental complexities of importing external modules, we've discovered collectively than the essential complexity is non-zero. Bringing a module into your project is non-trivially expensive. Bringing multiple modules into your project grows in expense super-linearly. (Not "exponentially", but definitely something g…

>We've come a lot farther than you may realize. We've come far enough that, having removed a lot of the accidental complexities of importing external modules, we've discovered collectively than the essential complexity is non-zero. Bringing a module into your project is non-trivially expensive. Bringing multiple modules into your project grows in expense super-linearly. (Not "exponentially", but definitely something greater than linearly.)

That's because those modules also have multiple (and competing) dependencies though.

If most modules in all languages depended on the same, lower level modules (with rigidly fixed APIs) that wouldn't the case.

Re: Autocomplete from Stack Overflow

#117
post #92

Earlier quoted context omitted.

I think that's part of the problem he's talking about. Why do new modules have to be made for a new framework? The framework should play nicely with standard modules written vanilla for that specific language. This way we're not staying over whenever a new framework is made.

Well there is CommonJS, and AMD modules. Many modules implement that in JS.

Those should delegate all the implementation to libs that work across languages (e.g. in C) and just provide a JS API for them. But they don't work that way, except for a very small number...

Re: Autocomplete from Stack Overflow

#118

Cool idea, but kind of ironic that the example you used produces unnecessarily complicated stack overflow solutions. A JavaScript "contains" function is as simple as: var contains = function (needle, haystack) { return haystack.indexOf(needle) !== -1 }

Older IEs don't have Array.indexOf(). So you either have to extend the Array prototype or, you know, just implement it in a more compatible way.

> Older IEs don't have Array.indexOf()

IE8 and older to be specific[0]. But, if you're supporting IE8 still you have bigger problems at hand.

Microsoft stopped supporting any version lower than IE11 as of January 12th of this year[1]. So unless all of those older IE machines are accessing an intranet (and only an intranet) their risk of being hit with malware is way higher than average.

For my clients I do a cursory IE9+ review, but if anything lower is a requirement then it's an additional fee to make a site work with it.

In a few months it'll be IE11+ and the same fee structure will apply to anything lower (I'm just waiting for IE10 to wind down a bit).

[0] http://caniuse.com/#search=array.indexof

[1] https://www.microsoft.com/en-us/WindowsForBusiness/End-of-IE...

Re: Autocomplete from Stack Overflow

#119

Earlier quoted context omitted.

Or just not support older IEs. http://browserupdate.org/

Maybe the likes of you someday will get a job and then understand that "what you support" does not depend on you.

Please don't post uncivil comments here.

Re: Autocomplete from Stack Overflow

#120
i did something similar one night a few months back, using python as a sublime plugin, but scrapes the live site. it eventually gets blocked tho as doesn't use the official API.

https://github.com/byteface/chode

I considered hooking into a variety of other resources but haven't really bothered with it as have other things going on.

Post reply on HN