| python |
Pythonタグが付けられた新着投稿 - Qiita |
ゼロから作るdeep learning 〜学習をスムーズに進めるためのメモ〜 |
https://qiita.com/vwnnbb3/items/b0c222fa9fccb466088b
|
deeplearning |
2023-06-05 02:40:44 |
| Git |
Gitタグが付けられた新着投稿 - Qiita |
【コピペで簡単】スプレッドシートをCSVにしてGitHubへプッシュする |
https://qiita.com/tamutamuta/items/b4e81ae1212e3327f9c6
|
github |
2023-06-05 02:52:14 |
| 海外TECH |
MakeUseOf |
Exynos vs. Snapdragon: Why Android Still Needs Samsung's Chips |
https://www.makeuseof.com/exynos-snapdragon-android-samsung/
|
android |
2023-06-04 17:01:17 |
| 海外TECH |
DEV Community |
World Wide Web Wars |
https://dev.to/andychiare/world-wide-web-wars-1h9p
|
World Wide Web WarsWhen I was a kid my grandfather used to tell me about his wartime adventures He served in both World War I and World War II He was a boy of I was interested in the entertaining side of the stories without understanding the suffering behind them One thing that stuck with me was that he often said that the two wars were different They were different in the way they were fought in the way they involved the population in their motivations Years later I find this thought about the two different wars applicable to a context that is fortunately less tragic than the one my grandfather experienced the World Wide Web In my career I ve been privileged to see the birth of the Web and its evolution from a platform for sharing documents to a platform for running distributed applications And along the way I ve witnessed a few wars I ll try to tell you about them as if I were your grandfather Make yourself comfortable it won t be short The HTML Centric EraIn the beginning the Web was based only on HTML and HTTP Nothing could be simpler documents were described using a simple markup language and transferred from one computer to another using a simple protocol Berners Lee s idea was simple and revolutionary at the same time And the key principle was interoperability Let s remember that word I started exploring the Web in the early s when Mosaic was the most advanced browser In those days you had to plan your Internet tour very well to avoid bleeding yourself dry with the time based tariff at least in Italy For a developer creating static HTML pages wasn t that exciting It didn t require any true programming skills The interesting part was to generate HTML dynamically on the server via the glorious CGI scripts Everything was quite clear and defined It didn t matter what kind of script you used on the server side Perl scripts shell scripts C programs What mattered was that its output was HTML and that it was transmitted over HTTP And the future looked bright The First Web WarThen in JavaScript came along and the scenario began to change The client side of the Web also needed development skills New browsers came out Netscape Navigator and Internet Explorer The first war began the browser war Browser builders basically Netscape and Microsoft competed to offer more and more attractive features support for animated GIFs new HTML tags e g marquee blink font support for scripting languages with little or no compatibility JavaScript JScript VBScript support for applets Flash objects ActiveX components etc It was a continuous explosion of new features but they were supported by only one browser and starting from a specific version There was a strategy later called EEE to defeat competitors with incompatible features Creating an interactive HTML page was a nightmare If you wanted the page to be usable by as many users as possible you had to take into account what features were supported by the browser and the version the users were using Browser sniffing techniques emerged which had to be kept up to date in order not to cut users off from your website To understand a bit what I mean try to take a look at some sample code from that era The alternative approach was to create web pages optimized for one specific browser an easier solution for the developer but a frustrating solution for the user All over the Web you could find sites with more or less elegant stickers inviting the user to use the browser for which the site was optimized So in that first Web war we had fierce competition among browser vendors to offer an increasingly advanced Web experience Developers had to deal with differences between browsers and between different versions of the same browser Many chose to optimize their pages for a particular browser much to the chagrin of users who experienced accessibility problems and were forced to use multiple browsers At the time the Web was not a good place for developers and users Nor was it for the interoperability that had been dreamed of The overall satisfaction with the Web could be summarized as follows UsersDevelopersBrowser vendors The Role of StandardsAt this point you may be wondering about the role of standards in all this confusion In particular what about the role of the WC In fact the consortium was responsible for defining a reference standard for web technologies primarily HTTP and HTML But at the time its influence and responsiveness was insufficient for a Web as dynamic as that of the late s Often the role of the WC was limited to defining as a standard those HTML features that were already de facto accepted For example iframe object and XMLHttpRequest were actually introduced by IE before they became standard So it was an a posteriori standardization that didn t bring much benefit to either developers and users Things began to change when the ECMAScript specification was released in JavaScript and other minor dialects had to conform to it to ensure compatibility across browsers But scripting language standardization alone was not enough That same year the WC defined DOM Level which moved browser interoperability in the right direction But we had to wait until for DOM Level standardization which stabilized the chaos that was occurring in web development That year the WC went further It defined XHTML a version of HTML based on the formally stricter criteria of the XML standard but with the advantage of extensibility Anyone could extend the language by providing the appropriate DTD or XML Schema The solution was technically sound but it was not fully understood and considered too complex In addition the lack of backward compatibility of XHTML with the old HTML caused many concerns This led to the formation of a new working group outside the WC the WHATWG whose goal was a reorganization of HTML that would eventually result in HTML XHTML was doomed to die within a few years The Invasion of External RuntimesAs in all wars there are those who get poor and those who take advantage During the browser war and the resulting lack of interoperability many developers turned to alternative technologies Many of them turned to Flash Java ActiveX and other technologies that offered more seamless development and a consistent user experience All they needed was install a runtime on the user s preferred browser At the time developing interactive and engaging web pages using HTML and JavaScript was a daunting task Alternative technologies such as Flash allowed an application to be downloaded locally to the browser and have only minor interactions with the server to retrieve data and update the user interface without having to reload the entire page A real revolution Unlike ActiveX which was tied to Internet Explorer and Windows Flash and Java applets guaranteed a consistent user experience regardless of the user s browser The price to pay was the use of proprietary technologies and some potential security risks that occasionally occurred The vision of the Web as a standard and interoperable environment began to crack Browser vendors simply supported external plugins to delegate app execution to Flash amp Co runtimes Developers who embraced this web programming model had the advantage of not having to worry anymore about which browser the user was using However they were no longer web developers in the proper sense they abandoned actual web technologies and specialized in developing for one or more of these runtimes Users could use the browser of their choice but they had to install and keep updated the different runtimes In short websites optimized for a particular browser had become websites optimized for a particular runtime not much of a gain after all While developers were quite comfortable once they chose their reference runtime users continued to suffer from the need to install different runtimes while keeping their browser of choice In summary this was the overall level of satisfaction UsersDevelopersBrowser vendors The JavaScript Centric EraWith the introduction of Ajax and dynamic DOM JavaScript and standard web technologies had their redemption Partial updates of a web page became a reality using standard technologies as well thanks to what was then known as Dynamic HTML DHTML JavaScript HTML and CSS were the standard triad of the Web By JavaScript was the real driver of sophisticated front end application development It was the new competitor to proprietary solutions like Flash Java and the others A few years later there was a historic changing of the guard for the Web Netscape Communicator successor to the glorious Netscape Navigator left the scene From its ashes the Mozilla project was born And that project would give birth to Firefox At the same time Chrome was born It was the dawn of a new Web era The Web Is JavaScriptThe resurgence of JavaScript and the desire to make the web ecosystem competitive against proprietary technologies gave a strong impetus to the proliferation of libraries aimed at simplifying DOM manipulation Ajax interaction with the server and integration with CSS In jQuery was born destined to become the most widely used library on the Web Soon MooTools Backbone Ember and others were there to compete with it Now developers had great allies to create dynamic and attractive web interfaces without reinventing the wheel The number of JavaScript libraries grew at an unprecedented rate Not a day went by without a new JavaScript library being born Ecosystems were created around some of these libraries i e libraries that specialize in a particular task but are based on specific core libraries For example jQuery UI is a library for building web interfaces that uses jQuery for DOM manipulation and other low level tasks Bootstrap was also born as a jQuery based UI library These libraries relieved the developer of the burden of having to work directly with HTML and CSS to create UI elements In addition they offered the advantage of handling the residual differences in standards support between different browsers admirably The developer s life was greatly simplified compared to the previous Web era The jQuery library became something of a standard and you could find it everywhere So much so that many junior developers had a hard time distinguishing jQuery from JavaScript and the DOM Many didn t even know what DOM was To many was a JavaScript feature Users lives also became easier in those years In general the experience of browsing and interacting with web pages was pretty consistent And users could use any browser they wanted except Internet Explorer and some later versions By now a web front end application was primarily a JavaScript application Developers simply had to choose the target library ecosystem and use compatible UI libraries Building a web UI became a matter of JavaScript code HTML was just a hook to pull code into the browser Rendering was dynamically performed by the base library s DOM manipulation You were in the era of Single Page Applications Soon came AngularJS and later React Shortly thereafter Vue arrived to complete the new triad of web front end development Yet Another Web War Today we can say that most front end development for the Web is based on these three ecosystems Angular React and Vue Can we say that there is a war going on If we compare the current situation to that of the first Web war we cannot say that there is the same kind of conflict In general browser vendors are ensuring some level of compliance with standards which are finally proactive The user s browsing experience does not suffer from the same problems as it did then But have we achieved that interoperability we dreamed of as a fundamental principle of the Web Looking more closely those who suffer from the lack of interoperability in the current situation are the front end developers In the first war they used to choose a browser and built pages optimized for it to make web development easier Now they are forced to choose a JavaScript ecosystem and build applications optimized for it On the user side of course there is a significant win Users don t care which JavaScript framework developers use And that s fair However developers cannot reuse the result of their work in another JavaScript framework A React component can only be used in a React application If you need the same component in an Angular or Vue application you have to recreate it In short the war between browsers is now a war between JavaScript frameworks Maybe a little quieter but not exempt from the occasional religious war The current situation can be summarized as follows UsersDevelopersBrowser vendors Back to the Web Platform Peace and Love The current war is not as loud as the browser war believe me it is not at all But that does not mean that it is not a problem Over the past few years I have witnessed a split in front end developer skills between the three major JavaScript frameworks I have also seen a loss of basic web platform standards skills It seems that there is a general loss of basic knowledge similar to what happened after the success of jQuery Several libraries simplify the developer s life and make up for the shortcomings of HTML JavaScript the DOM etc But in the meantime HTML has evolved JavaScript has evolved the DOM has evolved CSS has evolved The Web Components standard gives us with enough infrastructure to make the Web an interoperable platform for front end development Some people criticize this technology for being too low level but there are libraries that make the developer s life easier You might say that this is the same vicious cycle as JavaScript frameworks That s wrong because Web Components are interoperable by design Choosing Stencil or Lit or any other library is a development convenience that has little to do with the interoperability of the resulting components Do we really want to continue this silent war Wouldn t it be better to channel those energies into a standard ecosystem where everyone is free to use the tool of their choice to create components that can be used on the Web as a development platform Let s transform the Web from a platform for running applications to a platform for composing applications Let s add that missing piece to restore the original dream of an interoperable Web As a developer the next time you start a new project ask yourself this simple question do I really need a JavaScript framework Maybe it s time to bring some peace to the Web My grandfather and not just him would be happy |
2023-06-04 17:23:54 |
| ニュース |
BBC News - Home |
Bournemouth victim was fabulous young man - family |
https://www.bbc.co.uk/news/uk-england-65804301?at_medium=RSS&at_campaign=KARANGA
|
bright |
2023-06-04 17:32:41 |
| ニュース |
BBC News - Home |
Ukraine war: Anti-Putin fighters say two Russian soldiers 'captured' |
https://www.bbc.co.uk/news/world-europe-65804249?at_medium=RSS&at_campaign=KARANGA
|
agrees |
2023-06-04 17:44:10 |
| ニュース |
BBC News - Home |
French Open 2023 results: Novak Djokovic & Carlos Alcaraz through at Roland Garros |
https://www.bbc.co.uk/sport/tennis/65804225?at_medium=RSS&at_campaign=KARANGA
|
French Open results Novak Djokovic amp Carlos Alcaraz through at Roland GarrosNovak Djokovic beats Peru s Juan Pablo Varillas to reach a record th French Open men s singles quarter final with Carlos Alcaraz also progressing |
2023-06-04 17:25:29 |
| ニュース |
BBC News - Home |
Ashes 2023: Joe Root says England players can set themselves up for life with Ashes success |
https://www.bbc.co.uk/sport/cricket/65802705?at_medium=RSS&at_campaign=KARANGA
|
Ashes Joe Root says England players can set themselves up for life with Ashes successJoe Root says England s cricketers can set themselves up for life if they have a successful Ashes series this summer |
2023-06-04 17:06:19 |
| ビジネス |
ダイヤモンド・オンライン - 新着記事 |
【たった4年でFIREできた元会社員が教える】“働きたくないけれどお金は欲しい人”がやるべき2つのこと【書籍オンライン編集部セレクション】 - 投資をしながら自由に生きる |
https://diamond.jp/articles/-/323465
|
|
2023-06-05 02:55:00 |
| ビジネス |
ダイヤモンド・オンライン - 新着記事 |
「定義なんて、仕事では役に立たない」という誤解の落とし穴・ワースト1 - 新マーケティング原論 |
https://diamond.jp/articles/-/323902
|
|
2023-06-05 02:45:00 |
| ビジネス |
ダイヤモンド・オンライン - 新着記事 |
【精神科医が教える】 心を苦しめる「執着心」の最もシンプルな解決法 - 精神科医Tomyが教える 40代を後悔せず生きる言葉 |
https://diamond.jp/articles/-/322510
|
【精神科医が教える】心を苦しめる「執着心」の最もシンプルな解決法精神科医Tomyが教える代を後悔せず生きる言葉【大好評シリーズ万部突破】誰しも悩みや不安は尽きない。 |
2023-06-05 02:40:00 |
| ビジネス |
ダイヤモンド・オンライン - 新着記事 |
【小児科医が教える】「毎日食べてほしいキノコ」。栄養価的に一番おすすめの種類は？ - 医師が教える 子どもの食事 50の基本 |
https://diamond.jp/articles/-/323609
|
食事 |
2023-06-05 02:35:00 |
| ビジネス |
ダイヤモンド・オンライン - 新着記事 |
【英語でどう言う？】まあまあ、それなりに、かなり【5分で英会話力アップ】 - 5分間英単語 |
https://diamond.jp/articles/-/323470
|
【英語でどう言う】まあまあ、それなりに、かなり【分で英会話力アップ】分間英単語「たくさん勉強したのに英語を話せない……」。 |
2023-06-05 02:30:00 |
| ビジネス |
ダイヤモンド・オンライン - 新着記事 |
認知を変えるより、環境を変えることが「合理的に成功する」考え方の基本だ - シンプルで合理的な人生設計 |
https://diamond.jp/articles/-/323752
|
人生設計 |
2023-06-05 02:25:00 |
| ビジネス |
ダイヤモンド・オンライン - 新着記事 |
「いつも感じがいい人」が誰かと話す時に守るようにした、シンプルなルール - 機嫌のデザイン |
https://diamond.jp/articles/-/323948
|
「いつも感じがいい人」が誰かと話す時に守るようにした、シンプルなルール機嫌のデザイン「いつも他人と比べてしまう」「このままでいいのか、と焦る」「いつまでたっても自信が持てない…」。 |
2023-06-05 02:20:00 |
| ビジネス |
ダイヤモンド・オンライン - 新着記事 |
バブル期の日本経営者が恐れられていた 意外すぎる理由とは - CFO思考 |
https://diamond.jp/articles/-/323779
|
一橋大学 |
2023-06-05 02:15:00 |
| ビジネス |
ダイヤモンド・オンライン - 新着記事 |
仕事のできる人だけがやっている「単純作業」のひと工夫 - 20代が仕事で大切にしたいこと |
https://diamond.jp/articles/-/323654
|
単純作業 |
2023-06-05 02:15:00 |
コメント
コメントを投稿