In many computing contexts, "TTY" has become the name for any text terminal, such as an external console device, a user dialing into the system on a modem on a serial port device, a printing or graphical computer terminal on a computer's serial port or the RS-232 port on a USB-to-RS-232 converter attached to a computer's USB port, or even a terminal emulator application in the window system using a pseudoterminal device.

messy

Of course, there is no reason why you can't use <aside> for all sidenotes, if it makes your code simpler. Think of it as civil disobedience. :)

This shows that compatibility may be relevant.

A synonym of co-hyponym based on same tier (and not hyponymic) relation is allonym (which means "different name").

Tree structure

Semantic class

Currently, I’m working on designing the interfaces and it’s real fun!

click the images below

This content is not compatible on this device.

so you can learn about the ones you don't.

Conversely, red tests are tests I write after the code is written to lock down some implementation.

So the question becomes how many tests are enough?

I am a big advocate of having a complete test base and even erring on the side of caution when it comes to quality engineering and software validation but that is not what we’re talking about here. What we’re talking about here are the tests that we write when we’re doing test-first development and I’m proposing that writing those tests from the perspective of specifying the behaviors that we want to create is a highly valuable way of writing tests because it drives us to think at the right level of abstraction for creating behavioral tests and that allow us the freedom to refactor our code without breaking it.

As to opinions about the shortcomings of the language itself, or the standard run-times, it’s important to realize that every developer has a different background, different experience, different needs, temperament, values, and a slew of other cultural motivations and concerns — individual opinions will always be largely personal and, to some degree, non-technical in nature.

Married to Ruby, literally.

Money could be good if it is spent to provide some of the above things. Money on it's own is hard because then it means I would have to spend time book-keeping and managing instead of programming.

I think that's fine, but I also don't particularly care about @mikeycgto's desire to not have the linking comment be present in the minified JS.

I decided a couple of months ago to look for a way to work on faastRuby full time. Today is October 1st, 2019, and I am excited to announce that I am bringing faastRuby into Shopify.

If you plan on using a gamepad with big picture mode I made a config that works perfectly so check it out.

Usually when people are talking about code being semantically correct, they're referring to the code that accurately describes something.

Semantically correct usage of elements means that you use them for what they are meant to be used for.

It means that you're calling something what it actually is.

Brass tacks:

This is a non-exhaustive list of other things I love;

Spending an hour digging through bins in a record store is one of my favorite ways to clear my head. And then spend too much money.

Designing and writing code get me money so I can have food so they get a lot of my attention.

Fibar bi jàngal na taawan bu góor ni ñuy dagge reeni aloom.

the guard can also be a Callable-marked object

Currently, only Right signals are wired up.

While I certainly don’t think that all configuration should be “self hosted” in this kind of way

Instead of having this confusing maze of lambdas, regexes, and strings, we could, in theory, introduce a single entry point of configuration for Sprockets to use, and in that file declare all assets we wanted to compile. Well, that’s exactly what the manifest.js file is.

Before we get into what the manifest.js does, let’s look at what it is replacing.

Here's the last issue where source maps were discussed before the beta release.

keeps a semantic

Things could go wrong in two places here. First, the validation could fail if Github sends us data we don’t understand. Second, we might not know the user signing in, meaning the “find user” logic has to error-out

we also wrap them in Failure to solve the second problem: spotting potential exceptions is hard

exceptions are not exceptional, they represent expectable problems

Our mission is to allow people to make money via educational efforts and to dedicate the rest of their time to creating great open source products.

their main intent is to reduce fuzzy controller code

Trailblazer (TRB) is an Open-Source project. Since we want to keep it that way, we decided to raise awareness for the “cost” of our work - providing new versions and features is incredibly time-consuming for us, but we love what we do.

While Trailblazer offers you abstraction layers for all aspects of Ruby On Rails, it does not missionize you. Wherever you want, you may fall back to the "Rails Way" with fat models, monolithic controllers, global helpers, etc. This is not a bad thing, but allows you to step-wise introduce Trailblazer's encapsulation in your app without having to rewrite it.

Beware, though: What you are about to see is not particularly elegant. In fact, the TTY subsystem — while quite functional from a user's point of view — is a twisty little mess of special cases. To understand how this came to be, we have to go back in time.

This is in fact where I started, but this gives me all processes, which is exactly what I don't want.

Teaching is my passion

Some people believed I argued that object orientation is bad simply because extends has problems, as if the two concepts are equivalent. That's certainly not what I thought I said, so let me clarify some meta-issues.

If you think you’ve conveyed something but the other person hears something completely different, is that their fault or yours? 

From my perspective the onus is on you to consider not just the words coming out of your mouth, but how they are received.

Everyone has their own background and context that they overlay on top of what they hear. It’s our jobs as communicators to consider that perspective and to adjust the way we communicate accordingly. If we do, we stand a better chance of persuading them to agree with our point of view.

People often hear what they think should be said, not the words that are actually spoken. This comes from the tendency of people to think faster than they talk. A listener makes assumptions about what they expect because their minds race ahead. This can be especially problematic when you misinterpret what your boss said. 

My understanding of "programming to an interface" is different than what the question or the other answers suggest. Which is not to say that my understanding is correct, or that the things in the other answers aren't good ideas, just that they're not what I think of when I hear that term.

Rather than implement features you might need, you implement only the features you definitely need, but in a way that accommodates change. If you don't have this flexibility, parallel development simply isn't possible.

Unlike naming children, coding involves naming things on a daily basis. When you write code, naming things isn’t just hard, it’s a relentless demand for creativity. Fortunately, programmers are creative people.

We do know what our customers ask us for: powerful desktops and laptops that work with them in their creative endeavors. And we know that Canonical is no longer interested in catering to them. So we're going to try and step up.

Get off systemd, and enter the world of chroot.

You don't necessarily have to resize Windows' EFI partition. You can have multiple EFI partitions.

without grid-template-rows layout properties getting passed over to the next row

I disagree, but I can't downvote it, because it is an important POV.

Change any of the <option> by double clicking on the number.

Simple ways to do more with spreadsheets

You stick with what you know. It's trouble free because you know how to use it. That's achievable on any of the main OSs, even (gasp!) Windows.

You should default to the most permissive option imo and there really is no reason to check anything until you really need to If it were left to me I'd just use optional chaining, as it also eliminates the need for no-ops

In other words, programs that send messages to other machines (or to other programs on the same machine) should conform completely to the specifications, but programs that receive messages should accept non-conformant input as long as the meaning is clear.

be conservative in what you do, be liberal in what you accept from others

Progress is made of compromises, this implies that we have to consider not only disadvantages, but also the advantages. Advantages do very clearly outweigh disadvantages. This doesn’t mean it perfect, or that work shouldn’t continue to minimize and reduce the disadvantages, but just considering disadvantages is not the correct way.

The “no-snaps” ship already sailed years ago…you folks missed that boat. It’s too late to wish for a return to the past. Snaps in Ubuntu have been happening for years already, and will continue regardless of any opinions expressed here.

How do you know this? I've looked all over the internet and can't find any proof that Lightdm is more "lightweight" (whatever this means) or faster.

But, I am a little bit confused about what to do now, mark your answer as correct and create new question, or create and EDIT block to this post?

consume basic every day information and go around in different platforms meanwhile, without continuously consuming

capitulation-inducing poor performance

Nodes A wave function node occurs at points where the wave function is zero and changes signs. The electron has zero probability of being located at a node.

People really don't stress enough the importance of enjoying what you're programming. It aids creativity, makes you a better teammate, and makes it significantly easier to enter a state of flow. It should be considered an important factor in choosing a web development framework (or lack thereof). Kudos!

Find Your Passion, Then Monetize It The

Try a little of everything, and then choose a specialization. Money is not the most important thing. You need to LOVE your activity! But you don't know what you like until you try it.

Fallback values aren't used to fix the browser compatibility. If the browser doesn't support CSS custom Properties, the fallback value won't help.

I love the Material Design System’s buttons just because their principles are really well thought through.

we will look at the hierarchy of buttons and the language that they communicate

dfn export for=tree

passive: true instructs chrome that no body will call e.preventDefault() so chrome can optimized scrolling just because no body will call e.preventDefault and so there is no need to wait listeners...

I am curious how do you "organize" your work

I prefer light stock taking games like American Rails.

I find the binding of Mini Express pleasant.

Ultimately, I’m an “are there tough decisions?” kind of gamer, and on that matter I’m torn. There are some turns and some positions and some situations that will play themselves. Sometimes obviously so, and sometimes after you think it out.

I’m fan of maps (in real life and in games), and the map play here is interesting

What vaults this well past SNCF for me (setup time aside), is the limited company choice; it prevents a feedback loop of sorts where a game devolves into running each company in the ground.

M/F/D/V/L/G/B/T

I would suggest to follow an index convention for importing/exporting files

I'm excited for the RTM of webpack 2!

We are working to develop better communication within TC39 and with the broader JavaScript community so that this sort of problem can be corrected sooner in the future.

i like working on application frameworks, compilers, interpreters, and emulators.

but know I know what I don't want to do. I definitely know I want to be an Engineer now, and it makes it more clear that I should start my own business.

Tell you why tree-shaking fails, if it does.

What it doesn't do

Export plain functions

To appreciate the social role of Broca and his school,we must recognize that his statements about the brainsof women do not reflect an isolated prejudice toward asingle disadvantaged group. They must be weighed inthe context of a general theory that supportedcontemporary social distinctions as biologicallyordained.

If there are different tiers, those could be marked in the repo description (e.g. [COMMUNITY] or [UNSUPPORTED]).

I realise this is old, but as it isn’t a forum i see no problem in replying

will only apply up the chain

Investigate deeply.

dry-package

Things that I miss most from Vue:

What bothers me most from Svelte: <!-- I want to bind the value of this custom input just like I would bind to normal input --> <input bind:value="query" /> <!-- works --> <search-input bind:value="query" /> <!-- doesn't work :/ -->

Retagging the HTML/CSS questions to use html-heading seems the right thing to do. For the other uses, I don't have enough grounding in the geographic area to know whether the direction and bearing are replacements for heading. But the tag information for heading should be created and should firmly point at the other tags — at least until it is expunged.

We could broadcast a warning if we find the variable to be set in the environment, but that is more likely than not to annoy people who intentionally set it.

“"

Note that these are not hyperlinks; these URIs are used for identification. This is a machine-readable way to say “this is HTML”. In particular, software does not usually need to fetch these resources, and certainly does not need to fetch the same one over and over!

Don’t fetch stuff unless you actually need it Judging from the response to our 503 errors, much of the software requesting DTDs and schemata from our site doesn’t even need them in the first place, so requesting them just wastes bandwidth and slows down the application. If you don’t need it, don’t fetch it!

Anyone who’s ever worked with me knows that I place a very high value on what ends up checked-in to a source code repository.

The reason for this is very simple: once code gets checked-in, it takes on a life of its own.

Checking in is akin to sharing your code with others, and once out in the world, it’s hard to predict what that code will do.

Yet it can be deceivingly difficult to properly encode (user) input

E4X is a deprecated specification with deep reaching semantic meaning.

I prefer to have optionality over compound planing (assumptions, based on assumptions, …).

anti-fragile development

TOOAWTDI

Svelte should make something like useEffect part of the framework so that this could work better and be less verbose.

Although I'm starting to regret even posting this because I feel like it cheapens what we've accomplished.

I started Solid years ago before I thought anyone would be interested in using it. I only started promoting it because it had already achieved the goals I had set out for it.

JSX is an XML-like syntax extension to EcmaScript (https://facebook.github.io/jsx/). It is not a language or runtime.

perhaps, imo this would make more sense. but it would slow down Parcel significantly as packages who don't have a browserslist or something similar will all get compiled (and most packages actually do target commonjs, which makes this prob not such a good idea). Which unfortunately is way too many packages. It would be great if tools like babel actually enforced a similar pattern to Parcel and use browserlist file or package.json instead of allowing defining target env in babel. Or at least not encourage it.

You probably want initialValue! ⚠️ The value of the field upon creation. This value is only needed if you want your field be dirty upon creation (i.e. for its value to be different from its initial value).