I think Svelte has some things to learn from React hooks.

Why struggle with custom Syntax DSLs when you can use one so widely supported?

It was only pragmatic to use a tool that basically gives you that all for free.

Are there any rehearsal or set up dates on campus? Yes No Please enter any rehearsal or set up dates here

Because Svelte is a compiler, we're not bound to the peculiarities of JavaScript: we can design a component authoring experience, rather than having to fit it around the semantics of the language.

There are work arounds, but nothing clean. I just feel like this should be functionality that should be part of the slot feature.

I'm just pushing on the "is this really a good idea" front

You must: reference each element you are extending using refs or an id add code in your oncreate and ondestroy for each element you are extending, which could become quite a lot if you have a lot of elements needing extension (anchors, form inputs, etc.)

yet when I thought of my beloved Elizabeth, of her tears and endless sorrow, when she should find her lover so barbarously snatched from her, tears, the first I had shed for many months, streamed from my eyes,

Migrating the stores to TypeScript

“You are free to eat from any tree in the garden;(W) 17 but you must not eat from the tree of the knowledge of good and evil,(X) for when you eat from it you will certainly die.”

One key advantage of 'HTML-plus' languages is that you don't actually need tooling in order to be productive — most editors give you out-of-the-box support for things like syntax highlighting (though imperfect, as JavaScript expressions are treated as strings) and auto-closing tags. Tools like Emmet work with no additional setup. HTMLx should retain that benefit.

benefited from a shared set of tools for syntax highlighting, autocomplete, linting and so on.

Secure-by-default is a great approach, but this is not that. It's not even, we know what's best. It's clean up your act or you're out. You really should provide an opt-in to running with scissors. Maybe like config.opt_in_to_dynamic_routes_you_dumbass = true. 1 Pick your reaction

I too would like to know more about the security concerns that are the motivation to remove these useful dynamic routing components. The only thing I can think off is someone who accidentally exposes a private method public, is there more? The dynamic routes are a great way to keep the routing.rb DRY and avoid unneeded dependencies between the routing and the controller files, it has been quintessential Rails magic since version 1.0, surely there must be more serious security concerns to give up such important benefits? What are they? Do we really need to completely remove this from the code base, when removing it from the default routes.rb already would get you most of the security benefit?

I'm sure the security overlords have our best interest in mind and I'd be happy to change my opinion if someone can explain this tradeoff better. I know I can recreate the functionality for myself but I also like to keep in mind what's best for Rails. Just a hand wavy "we've had this for almost 10 years, but it might become an issue in the future so let's preventively eliminate it" does not seem a good enough reason to cut a feature that can make code much more DRY and elegant.

Sounds like Mixins are on their way out

If you are a senior, try talking to a junior or someone less experienced than you. Many companies are running what is called ”reverse mentoring” programs where juniors coach senior members of a company. Senior’s experience is traded for a fresh perspective from a junior. You’d be amazed at how much you could learn and share.

And on the topic of this particular article you need to own bigger mistakes too. It doesn't matter if the Apache board genuinely believed in 2014 that this was a good idea, it should now be obvious to everyone that it wasn't. Board members allowing it to continue can't fall back to "Well we didn't know...", because they do now. Every day that they have the evidence in front of them that the project is failing and do nothing they're _culpable_ for that as members of the board.

"that text has been removed from the official version on the Apache site." This itself is also not good. If you post "official" records but then quietly edit them over time, I have no choice but to assume bad faith in all the records I'm shown by you. Why should I believe anything Apache board members claim was "minuted" but which in fact it turns out they might have just edited into their records days, weeks or years later? One of the things I particularly watch for in modern news media (where no physical artefact captures whatever "mistakes" are published as once happened with newspapers) is whether when they inevitably correct a mistake they _acknowledge_ that or they instead just silently change things.

The carefully crafted Medium story can give the appearance that- at the nadir of your professional life- you are above it all, you are concerned about others, and you are a soulful human being moving on to an even more lucrative future.

Governments’ use of purchased location data has exploded in recent months, as officials around the world have sought insights on how people are moving around during the Covid-19 pandemic. In general, governments have assured their citizens that any location data collected by the marketing industry and used by public health entities is anonymous. But the movements of a phone give strong clues to its ownership—for example, where the phone is located during the evenings and overnight is likely where the phone owner lives. The identity of the phone’s owner can further be corroborated if their workplace, place of worship, therapist’s office or other information about their real-world activities are known to investigators.

But it has as an external service several disadvantages which opposed the philosophy of static websites diametrically.

The Rails team has decided to migrate all the talk, docs and core Google groups to  https://discuss.rubyonrails.org/.

but it launched with a plethora of issues that resulted in users rejecting it early on. Edge has since struggled to gain traction, thanks to its continued instability and lack of mindshare, from users and web developers.

Transition from Redcarpet to CommonMark

Bad people will always be motivated to go the extra mile to do bad things.

Meanwhile, criminals would just continue to use widely available (but less convenient) software to jump through hoops and keep having encrypted conversations.

The EARN IT act turns Section 230 protection into a hypocritical bargaining chip. At a high level, what the bill proposes is a system where companies have to earn Section 230 protection by following a set of designed-by-committee “best practices” that are extraordinarily unlikely to allow end-to-end encryption. Anyone who doesn’t comply with these recommendations will lose their Section 230 protection.

Broadly speaking, Section 230 of the Communications Decency Act protects online platforms in the United States from legal liability for the behavior of their users. In the absence of this protection, many of the apps and services that are critical to the way the internet functions today may have never been created in the first place – or they couldn’t have been created in America.

A year’s worth of cajoling back and forth has ultimately resulted in the EARN-IT bill wending its way through the U.S. system, a bill that, if passed, would see messaging services become legally responsible for the content on their platforms. While not mandating backdoors, per se, without some form of probes into message content, the argument runs that the punitive risks become unsurvivable.

there’s a bill tiptoeing through the U.S. Congress that could inflict the backdoor virus that law enforcement agencies have been trying to inflict on encryption for years... The choice for tech companies comes down to weakening their own encryption and endangering the privacy and security of all their users, or foregoing protections and potentially facing liability in a wave of lawsuits.

Once the platforms introduce backdoors, those arguing against such a move say, bad guys will inevitably steal the keys. Lawmakers have been clever. No mention of backdoors at all in the proposed legislation or the need to break encryption. If you transmit illegal or dangerous content, they argue, you will be held responsible. You decide how to do that. Clearly there are no options to some form of backdoor.

Despite its opposition, EARN-IT is the clearest threat yet to end-to-end encryption, given this clever twist in pushing the onus onto the platforms to avoid transmitting illegal content, rather than mandating a lawful interception approach.

Tiring of the privacy and safety debate, those behind EARN-IT have proposed making the platforms responsible for the content they transmit, encrypted or not. This would mean, as explained by Sophos, that tech companies “either weaken their own encryption and endanger the privacy and security of all their users, or forego protections and potentially face liability in a wave of lawsuits.”

The Digital Millennium Copyright Act (DMCA) has notable safe-harbor provisions which protect Internet service providers from the consequences of their users' actions. (Similarly, the EU directive on electronic commerce provides a similar provision of "mere conduit" which, while not exactly the same, serves much the same function as the DMCA safe harbor in this instance.)

and how moving to a monolith was the solution that worked for Segment.

Clients are updated to use the new service rather than the monolith endpoint. In the interim, steps such as database replication enable microservices to host their own storage even when transactions are still handled by the monolith. Eventually, all clients are migrated onto the new services. The monolith is "starved" (its services no longer called) until all functionality has been replaced. The combination of serverless and proxies can facilitate much of this migration.

I originally did not use this approach because many pages that require translation are behind authentication that cannot/should not be run through these proxies.

Mozilla does not permit extensions distributed through https://addons.mozilla.org/ to load external scripts. Mozilla does allow extensions to be externally distributed, but https://addons.mozilla.org/ is how most people discover extensions. The are still concerns: Google and Microsoft do not grant permission for others to distribute their "widget" scripts. Google's and Microsoft's "widget" scripts are minified. This prevents Mozilla's reviewers from being able to easily evaluate the code that is being distributed. Mozilla can reject an extension for this. Even if an extension author self-distributes, Mozilla can request the source code for the extension and halt its distribution for the same reason.

Territorial point of view

Add-ons must be self-contained and not load remote code for execution

Unfortunately, loading their code from their CDN is the only way those services permit their use.

Github Pages is a sweet service that builds your Jekyll site for you when you commit changes to a Github repo. If you were using redcarpet and Pygments, you now should switch to Kramdown and Rouge to stay updated with the recommended Markdown filter and syntax highlighter supported by Github Pages.

Switch from redcarpet to kramdown, the new Github Pages default

the Add functions seem to work generically over various types when looking at the invocations, but are considered to be two entirely distinct functions by the compiler for all intents and purposes

Recently the HaveIBeenPwned API has moved to a authenticated/paid model , this does not effect the PwnedPasswords API, no payment or authentication is required.

1Password wasn’t built in a vacuum. It was developed on top of open standards that anyone with the right skills can investigate, implement, and improve. Open tools are trusted, proven, and constantly getting better. Here’s how 1Password respects the principles behind the open tools on which it relies:

In addition, HBOT was found to reduce mortality rates from necrotizing fasciitis, and significantly decreased wound size in nonhealing diabetic wounds.

In the early 1990s, the creators of Netscape apparently built a function that enabled each web page to be annotated by those visiting it, as a way for viewers to discuss the page’s content. But according to a [1] produced in 2013 by a nonprofit called [Hypothesis][2], the feature was turned off.

The most common injuries from both blunt and penetrating thoracic trauma are hemothorax and pneumothorax. More than 85% of patients can be definitively treated with a chest tube. The indications for thoracotomy include significant initial or ongoing hemorrhage from the tube thoracostomy and specific imaging-identified diagnoses (Table 7-10). One caveat concerns the patient who presents after a delay. Even when the initial chest tube output is 1.5 L, if the output ceases and the lung is reexpanded, the patient may be managed nonoperatively if hemodynamically stable.

Automattic uses WordPress to power WordPress.com, and it contributes back code and time to the WordPress project. It is a symbiotic relationship. It isn’t accurate to say that WordPress is Automattic’s product, or that WordPress came from Automattic. Indeed, the opposite is true — Automattic came from WordPress, and Automattic (through WordPress.com) exists as part of the vast WordPress community and ecosystem.

While employees are used to working remotely every day, working parents are learning how work remotely with kids at home following mass closures of schools and child-care providers.

How do you leverage browser cache when Google’s very own Analytics.js has it’s expiry time set to 2 hours? How do you minimize DNS requests when Google advices you to copy their tracking code, linking to an externally hosted Javascript file?If that isn’t bad enough already, Google’s advice is to avoid hosting the JavaScript file locally. And why? To ensure you get access to new features and product updates.

Why should I host analytics.js locally?The Complete Analytics Optimization Suite for WordPress gives you the best of both worlds. After activation it automagically downloads the latest version of analytics.js from Google’s servers, places the necessary tracking code in your WordPress theme’s header and keeps the local Javascript file up-to-date using an adjusted version of Matthew Horne’s update analytics script and wp_cron(). This way you can minimize DNS requests, leverage browser cache, track your visitors and still follow Google’s recommendation to use the latest features and product updates.

Even one day a week out of the office might allow each employee to see their work in a new light.

Google Translate Widget

Another “decision” to make GoogleYoutube crappier and crappier with every passing day. The corporation seems stridently dedicated to deprecating its own products and abusing its customers.Search is now suckier than DuckDuckGo. Fuzzy and/or cherry-picked results.YouTube flooded with reposts/stolen vids and the “recommended” videos have literally nothing to do with your viewing behavior.Politicization and one-way censorship.Translator used to be nearly limitless (no text limit, websites translatable, etc) — now it’s basically a severely nerfed mini-tool to translate short phrases.

Unless you specifically need the open source tool, most website owners will be better served by the hosted version

We encourage all of our team members to take the time they need to recoup and refresh as much as they need.

Instant previews saw very low usage by our users, and we’ve decided to focus on streamlining the page to benefit more users.

the feature was dropped to “lack of use.”

Yes, it’s been deprecated. Why? Because too few people were using it to make it worth the time, money, and energy to maintain. In truth, although I sometimes disagree with the operator changes, I happen to agree with this one. Maintaining ALL of the synonyms takes real time and costs us real money. Supporting this operator also increases the complexity of the code base. By dropping support for it we can free up a bunch of resources that can be used for other, more globally powerful changes.

Time away from work It's important to clarify that being able to work from anywhere does not replace the need to take time off of work. We recognize how crucial it is to build in time where you can mentally take a break from your work, and as a company, we encourage our team members to do that. Learn more about how time off works at GitLab.

To never block or remove features from k6 in order to make them exclusive to Load Impact’s SaaS productStrive not to delay introduction of new features in the k6 OSS tool, if the feature was planned to appear both there and in Load Impact’s SaaS productTo never introduce into the k6 OSS tool any artificial limits designed to promote conversion to Load Impact’s SaaS productTo work with the community, participating in and prioritize building the functionality the k6 community wants, making it the prefered tool for load testing

With k6, our goal has always been to create the best load testing tool for the modern working developer and that we do this in collaboration with the k6 community. Our revenue will not come from k6 directly, but from premium value creating offers based on k6. These offers will be made available at https://loadimpact.com. Load Impact premium offers will have focus on providing further simplicity, productivity and ease to use functionality.

We believe the key to Load Impact’s long-term success as a Company is to foster an active community of users around k6 as an open source project. To achieve this long-term goal, it is vital that we do not withhold new features from k6 based on whether or not they compete with our SaaS offering.

Load Impact is a for profit organization, and recognizes that there is a need to balance this requirement with the needs of the k6 open source project. In the longer run, we strongly believe that those two needs will rarely be in conflict.

one that would borrow the best features from the ABC language

FYI for later travellers, it looks like the comment in question by @FreeSoftwareServer has been removed.

No backup regimen would be complete without testing. You should regularly test recovery of random files or entire directory structures to ensure not only that the backups are working, but that the data in the backups can be recovered for use after a disaster. I have seen too many instances where a backup could not be restored for one reason or another and valuable data was lost because the lack of testing prevented discovery of the problem.

In a nutshell, the King's Keys deck started as an experiment to see what card games would be like if you rebuilt playing cards from the ground up. Instead of using ranks and suits, each card has a number (from one to four), one of four items, and one of four colors. The result is what I call a 4x4x4 deck where 64 playing cards each have a unique combination of these three parts.

The url also contains an optional refspec (#v0.0.1) that tells npm which branch, commit, or in this case tag you want to have checked out.

By default, fetch() doesn’t provide a way to intercept requests, but it’s not hard to come up with a workaround. You can overwrite the global fetch method and define your own interceptor, like this

Moving forward with v7, we've decided it's best to stop publishing the Stage presets in Babel (e.g. @babel/preset-stage-0). We didn't make this decision lightly and wanted to show the context behind the interplay between TC39, Babel, and the community.

"neutrino-patch": "git+https://github.com/davidje13/neutrino-patch#semver:^1.0.1"