yeowMeng

Similar: http://codegolf.stackexchange.com/questions/55960/im-not-the...

I am no expert, but I always thought you could scrape without consequence provided you never distribute your scrapings?

I used to run Star Craft II on a a GNU/Linux laptop using WINE. The box would get hot AF, but it ran. I always thought WINE was impressive.

Alternatively: "How to build a low cost Linux cluster simulator using Pi's" :)

Canada, 10am-6pm, 1 hour lunch (30 mins paid).

And sometimes you find out data file Z is itself a Perl script :)

My experience with Perl:

We (a corporate shop) have a lot 'legacy' scripts in Perl.

I am assigned to maintain such scripts as no one else wants that role.

I discover, Perl is powerful.

Every 'legacy' script I find can be trivially regression tested (These scripts always have the same pattern, take some input, produce some output).

Managers want to move away from Perl.

I want to move closer to Perl.

> Scalability is achieved by distributing the documents across machines.

Unless everyone wants to edit the same doc at the same time.

I believe it is a reference to increased control over available gdb buffers (ex: register's value, disassembly, source). Ability to use macro's while debugging. And probably more key bindings.

Read at least two style guides for the lang of choice. Adopt the good ideas. Personally, I like the style guides published by Google.

I am not a pen tester, but I love paper cheat sheets on my desk. Currently: gdb, emacs, bash, operator precedance in C, register names/use in x86.

Especially Fortran in a unix MPI cluster.

The difference is when I update on iOS 9.something things will work.

When I update windows, I have to buy a new printer or, the headphone jack no longer works...

> Most jobs are just 'stuck in a loop' ones. Where you inherit legacy stuff and you're not allowed to change anything.

You are not allowed to change anything and commit it :) But it's amazing how much cruft you can dig out by say, re-writting the build system so that everything links dynamically and then running an address sanitizer build in dev env.

ie, datasets that are maintained and properly encrypted in a 'CEUE' (Create Encrypt, Update, Encrypt) app.

This is true. But Aboriginal's did execute controlled burns for reasons XYZ.

One reason for controlled burns was to create a funnel in a thick new growth area in order to funnel the herding animals for hunting purposes.

These controlled burns had successs in diminishing the risk of wild unstoppable fires.

Interesting fact: Aboriginal people living in North America before first contact with Europeans used to perform periodic controlled blazes on the land. Motivations including making the land easier for hunting and preventing uncontrollable fires from gaining strength.

Now, the land grows thick until fire comes to clean according to natures' idea of natural process.

I tree planted in BC/Alberta, the land grows so thick that they often have to fly you in helicopter to re-plant land that previous tree planters failed to plant correctly.

I stopped using these types of tools a while ago because I always disliked the bright flash that was created when the page was initially loading but before the plugin was executed. I would always try to take a long blink when I clicked a link lol.

Has this problem been solved shy from using lynx/emacs/ect?

Or alternatively, a digital impulse chemical continuum computer.

Features include: * No stack * Mostly type safe * Process complex thoughts known as emotions

Bugs: * ships without a C compiler * Consumes too much coffee * Version upgrades correlated to earth's rotation around the sun.

Wget/sh/sed/awk/perl soup

Anyone else like Bob Dylan... If people cheat, I believe there is a slow train comming.

Example: I had a friend who had an interview for company XYZ, "Write a program that clicks the first link in a wikipedia entry and exits when you reach the philosophy page (implement in the language of your choice). You have 15 mins"...

My friend was a really hard working, intelligent, and honest guy and he could not do it... i doubt cheaters could do it cold.

Unrelated but: It's easy to believe that yr peers are cheating. But I believe there are a lot of hard working people that know the concequence of cheating your way through.

Fair enough - bash has a lot of tough features to learn.

IMO, bash sticks around because a lot of people still find it useful.

Example: I have 2 mins to check if a duplicate line has occured in a log file with some arbitrary logging format. One pipeline later, I have an answer.

Disclaimer: I have only used vim and emacs, so I really don't know what an IDE can do.

Things I wish I knew about emacs earlier in life:

Emacs benifit plan volume 1:

* You will finally love the ui/ux for `info` pages

* macros (save and repeat a sequence of commands, commands can be applied to anything)

* registers (save locations in buffers, save text for later pasting)

* Frames (M-x speedbar for starters)

* modes (which to use and how to configure?!)

* built in documentation is awesome!

* what does this sequence of buttons do is only a `Ctr-h k <sequence of buttons>` away

* Mostly solid remote editing (tramp mode is no match for rsync on large files, luckily, RMS and friend have afforded us our freedom and we can configure this to our liking.)

* Freedom (as already identified by many people here but not by the word 'Freedom'. Also Freedom causes longevity. I have no source on this)

* Why is Freedom not number one on my silly list? If this were ORG mode I could bump it up to the top quickly.

* Excellent (multi-language (multi-language)) support. This is a recursive joke and the base case for me at least is English Bash. Emacs is language agnostic and language aware

* You will never have to write a 'throw-away' shell script ever again because emacs macros are that good. Still like shell scripting, incorporate shell commands in your macro.

* Carpel tunnel syndrom (cts) is a real thing, but, IMO, poor posture is more likely to give you health problems than cts. In reality, with Ctrl-R reverse search and Ctrl-S forward search, you can basically cycle through every command you have ever typed.

* Default key bindings in bash are emacs based and I actually enjoy the emacs bindings more than the vi ones despite spending lots of time in vim

Last reason: It's fun to play with a "real time display editor" and realize that emacs is an endless journey on the road to freedom in your ability to manipulate computation, however it may be expressed in years to come.

man pages could use a new section that literally contains @euske comment.

The new section should be called: 'Gotcha'.

I really enjoy this type of stuff, but always wonder why hateful words sometimes get melted in.

Edit: changed to existential claim.

Can you please GNU me yr 186 lines of bytes. I am curious.

http://radar.weather.gov/ridge/Conus/full_loop.php Radar for cross reference. Biggg giff

google-chrome not supported on arm